Skip to main content
Glama
Sign In

Taiwan Carbon Open Data (Unofficial)

by io.github.taux-io
OverviewDiscussionsAdmin

Calculate batch

calculate_batch
Read-onlyIdempotent

Calculate several activities at once, each with its own factor and source. A total is given only when every item succeeded and the items share a gas basis and boundary type; otherwise the reason is stated. 批次計算多筆活動，逐筆回傳結果與來源。只有全部成功、氣體基礎與邊界類型一致時才提供合計，否則說明不提供的原因。

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": {
      "items": "<items>"
    },
    "name": "calculate_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes要計算的活動，最多 50 筆。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, the description discloses a substantive behavioral rule: a total is returned only when every item succeeds and items share a gas basis and boundary type, otherwise a stated reason is returned. This is exactly the kind of output-shaping behavior annotations cannot convey. It stops short of 5 because per-item failure semantics beyond the reason string are not elaborated.

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

Conciseness3/5

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

The English content is front-loaded and earns its place, but the entire passage is then repeated verbatim in Chinese, effectively doubling length without adding information for a single-language reader. The aggregation rule appears before the item-level detail, which is the right ordering, but the duplication costs this dimension.

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 responsibly explains return semantics: aggregated total versus a stated reason for omission. Combined with full schema coverage of the items array, an agent has what it needs to call this correctly; only per-item failure reporting detail is missing.

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 description coverage is 100%, so nested item fields, unit guidance, and optional_context are already fully documented in the schema. The description's "each with its own factor and source" adds little beyond that, so the baseline 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 opens with a specific verb and resource ("Calculate several activities at once") and scopes the batch nature per item. The differentiation from the sibling calculate_emissions is only implied by "several ... at once" rather than stated, so it falls short of a 5.

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?

Batch-versus-single use is implied by "several activities at once", but no sibling is named and there are no explicit when-to-use or when-not-to-use conditions. An agent must infer that this replaces per-activity calculate_emissions calls.

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

All Taiwan Carbon Open Data (Unofficial) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources