Skip to main content
Glama
Sign In

Taiwan Carbon Open Data (Unofficial)

by io.github.taux-io
OverviewDiscussionsAdmin

Search emission factors

search_emission_factors
Read-onlyIdempotent

Search official Taiwan emission factors by keyword, category, type, year or unit. Returns factor IDs to pass to get_emission_factor and calculate_emissions. Covers electricity, tap water, fuel combustion, refrigerants and other fluorinated gases (GWP values), and product carbon footprint factors; returns an explicit not-found message rather than a near match. Refrigerant blends such as R-410A are not listed: pass their components as refrigerant_blend to calculate_emissions, calculate_batch, compare_emissions or build_inventory. 以關鍵字、類別、類型、年度或單位搜尋台灣官方排放係數，回傳的係數 ID 可交給 get_emission_factor 與 calculate_emissions。目前收錄電力、自來水、燃料燃燒、冷媒等含氟氣體（溫暖化潛勢）與產品碳足跡；查不到會明確說明，不會給相近的替代品。R-410A 這類混合冷媒不在表內，請把成分以 refrigerant_blend 交給 calculate_emissions、calculate_batch、compare_emissions 或 build_inventory 計算。

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": "search_emission_factors"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNo係數分母的單位，例如 kWh、m3、TJ。
yearNo適用年度（西元）。
limitNo回傳筆數，預設 10，上限 50。
queryNo關鍵字，繁體中文或英文，例如 電力、柴油、自來水、gasoline。多個關鍵字以空白分隔。
offsetNo略過前幾筆（分頁用）。
categoryNo類別：electricity 電力、water 自來水、fuel_combustion 燃料燃燒、refrigerant 冷媒等含氟氣體、product_footprint 產品碳足跡。
factor_typeNo係數類型，用來區分固定燃燒與移動燃燒等。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, but the description adds genuinely non-redundant behavior: coverage boundaries (electricity, water, fuel combustion, refrigerants/GWP, product footprint) and, most importantly, that a miss returns an explicit not-found message rather than a near match. That prevents an agent from hallucinating a fuzzy result. The only untold behavior is result ordering, which is minor for a read-only search.

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 content is well front-loaded and every claim is substantive, but the entire passage is presented twice, once in English and once in Chinese, doubling token cost without adding information for any single reader. A locale note or a single language would earn a higher score; the duplication is a real structural cost against an otherwise tight statement.

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, and the description compensates by telling the agent what comes back — factor IDs intended for get_emission_factor and calculate_emissions — plus the failure mode (explicit not-found). For a 7-parameter, fully optional, read-only search tool, nothing needed to invoke or interpret it 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% and includes enums with Chinese glosses for category and factor_type, so the schema does the heavy lifting. The description enumerates the searchable fields but adds no syntax or format meaning beyond what the schema already states (e.g. multi-keyword space separation, default limit 10, max 50 are all schema-level). Baseline 3 applies.

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?

Names a specific verb and resource plus the full searchable dimension set (keyword, category, type, year, unit), and distinguishes itself from siblings by stating it 'Returns factor IDs to pass to get_emission_factor and calculate_emissions' — i.e. it retrieves, it does not compute. An agent can tell it apart from calculate_emissions or get_emission_factor without opening a schema.

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?

Explicitly routes downstream work: search here, then hand the returned IDs to get_emission_factor or calculate_emissions. It also names a concrete exclusion case (R-410A and other blends are not listed) and names the exact alternative path — refrigerant_blend on calculate_emissions, calculate_batch, compare_emissions or build_inventory — so the agent knows both when not to use this tool and what to do instead.

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