Loading ToolBench
MCP server that provides gold price data from the DAYLY GOLD API
Single tool with critical definition gaps. Description is present (47 chars) but minimal and lacks context on when/why to use it, what it returns, or error handling. No parameter descriptions exist (none needed given empty schema), but the tool provides no output schema documentation. The implementation returns unstructured text rather than structured JSON. No error recovery guidance. Logging is present but does not compensate for definition quality gaps.
Get the gold price from the DAYLY GOLD API.
Input schema is empty ({}). Tool accepts no parameters, which is valid, but schema must be explicitly documented as an empty object with proper JSON Schema structure.
No output schema documented. Tool returns unstructured text (multi-line string) instead of structured JSON. LLMs cannot parse or chain results. Should return {price: string, date: string, change: string, changePercentage: string, market: string, highest: string, lowest: string, open: string, previousSettlement: string, updateTime: string}.
Description is 47 characters and lacks actionable context. Does not explain WHEN to call this tool, WHAT it returns, or HOW to use the result. Should be 50-200 chars and answer: what data? what format? any prerequisites?
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 29 | <=2025-11-25 | v2 |
No error handling guidance. If API fails (network timeout, invalid key, malformed response), tool returns generic error strings. LLM has no recovery path. Should categorize errors (retryable vs fatal) and suggest next steps.
API key hardcoded in source code. Security violation: credentials must never appear in tool parameters or source. Use environment variable injection (os.getenv('DAYLY_GOLD_API_KEY')) and document the required env var in server setup.