Loading ToolBench
Stdio bridge to Sourcey's live MCP server for startup credits, deals, and agent readiness
Single tool 'search_offers' has a minimal schema with only a 'query' string parameter and no description of what the parameter controls. The tool description is generic (10 words) and lacks context on when to use it, what it returns, or how results are structured. No output schema is documented. The tool name lacks a clear action verb pattern and the parameter lacks type constraints or format guidance. This server appears to be a bridge to an external Sourcey service, but the tool definition itself is severely underdocumented.
Search current startup credits and deals.
Tool description is too short (10 words, 54 chars). Minimum 20 chars required; should be 50-200 chars explaining WHAT it does, WHEN to use it, and WHAT it returns.
Parameter 'query' has no description. LLMs cannot infer what 'query' should contain (free text? keywords? filters?). Every parameter must have a non-empty description.
No output schema documented. LLMs need to know what fields to expect in the response (e.g., offer_id, title, description, expiration_date, credit_amount). Without this, agents cannot plan downstream actions.
Tool name 'search_offers' is acceptable but generic. Consider 'search_startup_credits' or 'search_startup_deals' to match the description's mention of 'startup credits and deals'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2025-06-18+ | v2 |
No error handling guidance. If a query returns no results, or if the upstream Sourcey service is unavailable, what should the LLM do? Provide recovery hints in error responses.