Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_list_data_versions

Read-onlyIdempotent

Lists ClimeqAI emission factor catalog releases, version statistics, included datasets, and markdown changelogs so you can identify the data version behind carbon calculations.

Instructions

List ClimeqAI emission factor catalog releases, release statistics, datasets, and markdown changelogs.

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_data_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds the concrete payload categories (releases, statistics, datasets, changelogs) but says nothing about pagination, size, ordering, authentication, or caching behavior for an open-world listing call.

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?

A single front-loaded sentence with the verb first and the four returned categories enumerated. There is no filler, hedging, or repetition, and nothing an agent must read past to reach the operative information.

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?

With no output schema, the description usefully enumerates what comes back, which is the main completeness risk for a zero-parameter listing tool. It stops short of describing the shape of those payloads or whether all four categories are always returned, but for a simple catalog listing it is largely sufficient.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema is empty and fully described, leaving nothing for the description to compensate for.

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 pairs the verb "List" with a specific resource set: ClimeqAI emission factor catalog releases, release statistics, datasets, and changelogs. This resolves the ambiguity in the name "data_versions" and tells an agent it retrieves catalog metadata rather than emission values. It does not reference any sibling, but the sibling set is dominated by calculate_* tools that do not overlap with this read-only catalog listing.

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 only implied: an agent can infer this is the discovery step for catalog releases and changelogs, likely before searching or calculating. There is no explicit when-to-use statement, no prerequisites, and no mention of the alternative metadata tools such as climeq_list_regions or climeq_list_unit_types.

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