Advanced: List trading strategies for a thesis.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | Yes | SimpleFunctions API key. Get one at https://simplefunctions.dev/dashboard/keys | |
| status | No | Filter: active|watching|executed|cancelled|review | |
| thesisId | Yes | Thesis ID |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden for behavioral disclosure. It does not mention return format, pagination, read-only nature, or authentication requirements beyond the schema's apiKey field.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise but under-specified. The 'Advanced:' prefix adds no value, and the single sentence provides minimal context without wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description omits key context about what strategies are, how they relate to a thesis, and the optional status filter. For a simple tool with no output schema, more guidance is needed for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists trading strategies for a thesis, using a specific verb and resource. However, it does not differentiate from sibling list tools like list_intents or list_theses.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as list_theses or get_strategies. The 'Advanced' prefix hints at user level but not contextual usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping purposes, such as multiple market query tools (scan_markets, screen_markets, get_market_detail, get_market_diff, get_market_history, inspect_ticker) and legislative tools (legislation, get_legislation, list_legislation, query_gov). Aliases like get_heartbeat_config/get_heartbeat_status and explore_public/explore_theses add further confusion. An agent would struggle to select the correct tool without deeply reading each description.
Most tools follow a verb_noun pattern (get_, list_, create_, update_), but there are notable deviations: 'legislation' lacks the 'get_' prefix, 'stt' and 'tts' are acronyms, 'monitor_the_situation' is a full phrase, and 'x_account/x_news/x_volume' use a non-standard prefix. The overall style is readable, but the mixed conventions reduce predictability.
108 tools is extreme for any server, even one covering prediction markets, trading, portfolio management, forum, skills, and speech. The massive surface area overwhelms agents and makes the server feel more like a platform than a coherent toolkit. This many tools inevitably leads to redundancy and maintenance burden.
The server covers an impressively broad domain: market data, thesis management, intents, strategies, positions, portfolio, forum, skills, legislative and economic queries, and audio/visual processing. Minor gaps exist (e.g., no delete for skills/theses, no update for some portfolio items) but core workflows are well-supported. Overall lifecycle coverage for most entities is strong.
