Climate MCP Server

fund_summary

Access a fund's structured profile with metadata, stage metrics, portfolio share, and conversion ratios (e.g., deposit to pledge).

Instructions

    Structured profile card for one fund: metadata, all four stage metrics,
    portfolio share, and stage conversion ratios (deposit/pledge, etc.).
    Combines B's fund_summary with A's fund_conversion_ratios into one call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fund_id": "<fund_id>"
    },
    "name": "fund_summary"
  }
}

Input Schema

Name	Required	Description	Default
`fund_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description only covers output contents. It does not disclose whether the tool is read-only, requires specific permissions, has rate limits, or any side effects. The behavioral traits are not addressed beyond what can be inferred.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no extraneous information. It front-loads the core purpose in the first sentence and adds context in the second. Every part contributes to understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema (not shown), the description need not detail return structure, but it lists key components. It lacks prerequisites, error conditions, or examples. For a simple one-parameter tool with a composite output, the description is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only implies that 'fund_id' identifies the fund. It does not explain the parameter's format, range, or any constraints beyond the schema's 'integer' type. The description compensates only minimally for the lack of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool produces a 'structured profile card' including metadata, four stage metrics, portfolio share, and conversion ratios. It explicitly distinguishes itself from siblings by noting it combines two separate functions (B's fund_summary and A's fund_conversion_ratios).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its use when both fund summary and conversion ratios are needed together, but it does not explicitly state when to use this versus alternatives like 'get_fund_details' or 'fund_conversion_ratios'. No when-not or exclusion criteria are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.