Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_search_factors

Read-onlyIdempotent

Search governed global and organization-owned private emission factors using filters for region, year, category, source, unit type, and data version to support carbon calculations.

Instructions

Search ClimeqAI governed global emission factor datasets and organization-owned private factors with optional filters for region, year, category, source, unitType, and dataVersion.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
yearNoReference validity year (e.g., 2025).
queryNoSearch keywords (e.g., 'structural steel', 'natural gas').
regionNoISO country or region code (e.g., 'TR', 'DE', 'EU', 'US').
sourceNoDataset source filter (e.g., 'DEFRA', 'EPA', 'EXIOBASE').
categoryNoOptional category filter.
pageSizeNo
unitTypeNoUnit family (e.g., 'Weight', 'Energy', 'Money', 'Distance').
dataVersionNoCatalog release selector (e.g., '^2026.1', '2026.1').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description usefully adds that two corpora are searched in one call (governed global plus organization-owned private factors), but says nothing about result caps, the max page of 5, or what happens when filters match nothing.

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?

One front-loaded sentence with the resource and scope stated before the filter list. It is efficient, though the trailing filter enumeration duplicates schema descriptions and could be trimmed without loss.

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 9 parameters, no required ones, and no output schema, the definition should say more about what a result record contains and how paging behaves. It is adequate to select and call the tool but leaves the agent to infer result shape and pagination behavior.

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?

At 78% schema coverage the schema carries most parameter meaning, and the description's enumerated filter list largely restates it. Marginal added value comes from labeling the filters 'optional', but the query field's matching behavior (keyword vs. exact) and the dataVersion selector syntax remain unexplained in both places.

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?

States a specific verb ('Search') and a precisely scoped resource (ClimeqAI governed global emission factor datasets plus organization-owned private factors), which clearly separates it from the calculate_* and list_* siblings. It stops short of explicitly naming which sibling to use instead when browsing rather than searching.

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?

No when-to-use or when-not-to-use guidance is given; the agent must infer that this is a discovery step preceding a calculate_* call. There is no mention of climeq_list_private_factors as the alternative for enumerating private factors, nor of any prerequisite such as an org context.

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