Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_list_regions

Read-onlyIdempotent

Search canonical ISO-3166 country codes, continental/sub-national zones, and hierarchical geographic fallback chains to map regions accurately for emissions and carbon workflows.

Instructions

Discover canonical ISO-3166 country codes, continental/sub-national zones, and hierarchical geographic fallback chains.

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": "climeq_list_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOptional code or country name filter (e.g., 'TR', 'Germany').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds useful domain context about canonical codes and fallback chains, but does not explain filtering behavior, result shape, or pagination, so it adds only moderate value beyond the structured annotations.

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 definition is a single front-loaded sentence with no redundant wording. Every phrase contributes to identifying the geographic reference data available.

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?

For a simple one-optional-parameter discovery tool with complete schema descriptions and rich annotations, the description covers the key data categories. It could be slightly stronger by noting that the tool supports filtering, but no output schema is expected and the core behavior is sufficiently described.

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

Parameters3/5

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

Schema coverage is 100%, and the single optional search parameter is already documented with examples in the schema. The description does not mention the search filter at all, so it adds no parameter meaning beyond the schema; the high-coverage baseline of 3 applies.

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 states a concrete discovery purpose: canonical ISO-3166 country codes, continental/sub-national zones, and hierarchical fallback chains. It clearly identifies the resource, though it does not explicitly contrast itself with sibling lookup/list tools.

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?

Usage is implied as a reference-data lookup, but there is no explicit guidance on when to call this tool versus calculate or other list tools, nor any prerequisites or sequencing advice. The name and description make its role inferable, but an agent must infer it.

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