Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_procurement_spend

Calculate Scope 3 Category 1 spend-based emissions from procurement amounts, applying EXIOBASE price margins and IMF CPI inflation adjustment.

Instructions

Calculate Scope 3 Category 1 spend-based emissions using EXIOBASE Basic Price margin stripping and IMF WEO CPI inflation adjustment.

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": {
      "amount": "<amount>",
      "currency": "<currency>",
      "category": "<category>"
    },
    "name": "climeq_calculate_procurement_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
persistNo
categoryYesSpend category or description (e.g., 'IT_SERVICES', 'STEEL').
currencyYesISO 4217 currency code (e.g., 'EUR', 'USD', 'TRY').
spendYearNo
countryCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutating, external-data operation. The description adds real methodology context (margin stripping, CPI adjustment) that explains the calculation approach, but it never mentions that pass-through to EXIOBASE/IMF is external, or what the 'persist' flag does when it writes results.

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?

A single dense sentence with no filler, and the core action is front-loaded. The jargon is heavy but every clause (methodology, margin stripping, CPI) carries information rather than restating the tool name.

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

Completeness2/5

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

With six parameters, no output schema, and only partial annotations, the description should say more: the unit and basis of the returned emissions figure, how countryCode and spendYear affect the result, and what persist does. Those gaps matter for a calculation tool whose output has no schema to document it.

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 only 33%: category and currency are documented, but amount, spendYear, countryCode and persist are not. The description hints at spendYear via 'CPI inflation adjustment' but never explains that countryCode selects an EXIOBASE region or what persist controls, leaving half the parameters without meaning in either field.

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 and resource: 'Calculate Scope 3 Category 1 spend-based emissions', with the methodology named (EXIOBASE Basic Price margin stripping, IMF WEO CPI adjustment). That resource is specific enough to separate it from siblings like climeq_calculate_air_travel or climeq_calculate_electricity, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. An agent must infer from the words 'spend-based' that this applies to monetary procurement data rather than activity-based methods, which is implied usage at best.

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