Taiwan Carbon Open Data (Unofficial)

Match activity to candidate factors

match_activity

Read-onlyIdempotent

Map an activity or ledger-account description (for example an electricity bill, fleet fuel, or a plastic resin purchase) plus an optional unit to candidate official factors. Returns candidates with unit compatibility, applicability conditions and the questions the user must answer; it never picks one. Use this when the user's wording is not an official factor name, then confirm with the user before calling calculate_emissions. The term mapping is curated by this service, not official. 把活動或會計科目的描述（例如電費、公務車加油、塑膠原料採購）與單位對到候選的官方係數，回傳每筆的單位相容性、適用條件與需要使用者回答的問題；不會代為選定。使用者的說法不是官方係數名稱時用這個工具，並在呼叫 calculate_emissions 之前先向使用者確認。用詞對照是本服務整理的，不是官方資料。

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": {
      "description": "<description>"
    },
    "name": "match_activity"
  }
}

Input Schema

Name	Required	Description
`unit`	No	活動數據的單位，例如 kWh、度、L、kg。有給就會檢查每筆候選的單位是否相容。
`year`	No	活動發生的年度（西元）。不給時，逐年公布的係數只列最新年度。
`limit`	No	回傳的候選筆數，預設 10，上限 25。
`description`	Yes	活動或會計科目的描述，例如「10 月電費」「公務車加油」「塑膠原料採購」。

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses what the response contains (unit compatibility, applicability conditions, open questions), states the tool never selects a factor, and warns that the term mapping is curated by the service rather than official. That last caveat is a meaningful trust signal an agent could not infer from the annotations.

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?

Each language version is front-loaded and efficient, but the full text is duplicated in English and Chinese, roughly doubling the length. This is intentional and consistent across the definition, but it costs some density.

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

Completeness5/5

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

There is no output schema, yet the description explains the shape of the return value (candidates with unit compatibility, conditions, and questions), which is exactly what an agent needs for a read-only matching tool. It also makes the failure and confirmation path explicit, leaving no critical gap.

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%, so all four parameters are already documented in the schema, and this sets the baseline at 3. The description reinforces the description parameter's purpose and the optional unit, along with the year and limit parameters that appear in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise verb and resource: it maps an activity or ledger-account description plus an optional unit onto candidate official factors. It supplies concrete examples (electricity bill, fleet fuel, plastic resin purchase) and distinguishes itself from sibling tools by noting that it never picks a factor and must be followed by calculate_emissions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger (when the user's wording is not an official factor name) and an explicit next step (confirm with the user before calling calculate_emissions). The boundary against search_emission_factors and calculate_emissions is therefore clear from the definition alone.

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) tools Inspect

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.