Skip to main content
Glama

get_climate_risk_benchmark

Read-only

Climate financial risk benchmarks — physical risk (flood, hurricane, wildfire, heat), transition risk (carbon pricing scenarios, stranded assets), and lender implications. Source: FEMA NFIP, NGFS scenarios. For ESG and risk agents. $0.02 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_climate_risk_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo
risk_typeNo
property_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context the annotations do not carry: upstream data provenance (FEMA NFIP, NGFS scenarios) and a per-call cost of $0.02 USDC, which materially affects whether an agent should call it repeatedly. Return shape and latency remain undisclosed.

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

Conciseness4/5

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

Three tight fragments, front-loaded with the resource and its risk taxonomy, with provenance and price trailing. No filler sentences, though the segmented phrasing reads slightly like marketing copy rather than specification.

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

Completeness3/5

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

With no output schema, no annotation detail on returns, and zero parameter descriptions, the definition leaves real gaps: the agent knows what data sources feed the benchmark and what it costs, but not what a response contains, what units a benchmark is in, or how region and property_type change the result.

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%, so the description must carry all parameter meaning. It partially compensates for risk_type by naming physical and transition categories, but says nothing about what 'region' values such as southeast or national mean, nor about property_type or the 'all' enum option. Two of three parameters are left entirely to bare enum values.

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

Purpose4/5

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

The description names a specific resource (climate financial risk benchmarks) and enumerates what it covers: physical risk (flood, hurricane, wildfire, heat) and transition risk (carbon pricing scenarios, stranded assets). It does not, however, distinguish itself from the closely-named sibling get_climate_risk_score, leaving an agent to infer whether 'benchmark' versus 'score' is the right call.

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

Usage Guidelines2/5

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

'For ESG and risk agents' identifies a target audience but gives no when-to-use or when-not-to-use condition, and never routes the agent to the obvious alternative get_climate_risk_score. The agent must infer the choice from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources