get_market_summaryOne call for orientation: how much of the archive is available, when it last updated, the story-tag breakdown (use these as tag values for search_news), and the current price table. Start here.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations already communicate that this is a safe, read-only call in an open world, so the description's main job is to add context. It does add content and cross-tool coupling, but it does not disclose any additional behavioral traits such as staleness, rate limits, or response-shape caveats.
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 a single front-loaded sentence that starts with the key idea ('One call for orientation') and then presents a scannable list of contents. The final 'Start here.' is short, purposeful guidance with no filler.
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?
With no parameters, no output schema, and annotations covering safety, the description carries the full burden of explaining what the agent will get and when to use it. It explains all major output categories and links the story tags to search_news, making the call actionable end to end.
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?
The tool has zero parameters and an empty input schema, so there is no parameter semantic burcen. The 0-parameter baseline of 4 applies; the description appropriately focuses on what the output contains instead.
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 states a specific purpose ('One call for orientation') and enumerates the exact contents: archive availability, last updated, story-tag breakdown, and current price table. This distinguishes it from sibling tools like get_price_history or search_news by describing a cross-cutting summary rather than a targeted retrieval.
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?
'Start here' explicitly tells the agent when to make this call, and the note to use its story tags as tag values for search_news gives concrete follow-up guidance. It does not spell out when not to use each sibling, but the orientation framing provides clear usage context.
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.
Each tool has a generally distinct purpose, but get_market_summary includes a current price table that overlaps with get_carbon_prices. The descriptions mitigate this by clarifying that get_market_summary is for orientation while get_carbon_prices provides detailed price data from two non-comparable sources.
All tool names follow a consistent verb_noun pattern in snake_case: get_carbon_prices, get_market_summary, get_price_history, get_story, list_sources, and search_news. The naming is predictable and clearly indicates the returned resource.
Six tools is a well-scoped size for a carbon market data and news retrieval server. Each tool covers a distinct need without unnecessary redundancy or bloat.
The tool surface covers the core read-only workflows: current prices, historical prices, market orientation, news search, story retrieval by id, and source coverage discovery. The workflows connect naturally, e.g., get_market_summary provides tags for search_news, and search_news results can be followed by get_story.