list_sourcesThe publications, registries and integrity bodies carbon.fyi monitors. Useful for judging coverage — a topic absent from the archive may simply not be covered by these sources.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and openWorldHint=false. The description adds interpretative context about the closed-world nature of the list and its role in coverage judgments, which goes beyond the structured annotation fields.
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?
Two sentence description with no wasted words. The first sentence states what the tool returns, and the second sentence explains its practical value. Highly efficient and well-structured.
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?
For a zero-parameter, read-only metadata listing tool, the description fully covers what is returned and how to interpret it. No output schema exists, but the simplicity of the tool does not demand more detail.
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 the schema coverage is 100%, so there is no parameter information lacking. The description is not required to explain parameters that do not exist.
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 identifies the resource ('the publications, registries and integrity bodies carbon.fyi monitors') and the operation is implied by the tool name 'list'. It is clearly differentiated from siblings, which deal with prices, summaries, history, stories, and news search.
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?
The description provides a concrete use case: 'Useful for judging coverage — a topic absent from the archive may simply not be covered by these sources.' This gives clear context for when to use the tool, though it does not explicitly mention alternatives or when not to use it.
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.