api

search_factors

Find emission factors by section, key prefix, or free text. Returns each match with its key, name, section, VALUE, unit and gas — enough to choose between them or read a few numbers without a second call. For one factor's full audit envelope (publisher, exact source cell, retrieval date, licence, verification) call lookup_factor; for several, call lookup_factors.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 20).
`query`	No	Free-text search over factor names/keys.
`section`	No	Restrict to a section, e.g. "grid", "fuels", "freight".
`key_prefix`	No	Restrict to keys starting with this prefix.

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It honestly describes the returned fields and clarifies that full audit details are intentionally deferred to lookup tools. It does not describe match semantics or empty-result/pagination behavior, so it is not quite a 5.

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

Conciseness5/5

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

Three dense sentences with no filler. The primary purpose is front-loaded, the return contract is summarized, and the routing guidance is placed at the end.

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?

The description is complete for this tool category: it covers what is searched, what is returned, what is omitted, and which sibling tools cover the omitted case. Since there is no output schema, explicitly naming the returned fields is valuable and sufficient.

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 all four parameters are already documented. The description echoes the search modes by mentioning section, key prefix, and free text, but it does not add any meaning beyond 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 clear verb and resource: 'Find emission factors by section, key prefix, or free text.' It also lists the exact fields returned, which immediately differentiates it from lookup_factor and lookup_factors.

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 explicitly says when to switch to alternatives: 'for one factor's full audit envelope ... call lookup_factor; for several, call lookup_factors.' This gives the agent a concrete routing decision rather than leaving it to infer.

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

All api tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct role: search, lookup single, lookup batch, resolution, absence explanation, and separate calculation methods for distinct scopes. Even the discovery tools can be told apart by whether the input is a key, text, natural language, or a purpose. Domain calculators are cleanly separated by type of activity, so an agent should not confuse them.

Naming Consistency5/5

All tools follow a consistent verb_nonn pattern: calculate_*, lookup_factor(s), search_factors, resolve_factor, explain_absence. The naming clearly signals both action and object, and even the singular/plur lookup distinction matches the batch versus single-key semantic.

Tool Count5/5

Twelve tools is well-sopened for a broad emissons-factor API: six calculators, four discovery/lookup/resolution tools, one batch lookup, and one edge-case explainer. Each tool appears to serve a necessary purpose rather than adding redundant surface area.

Completeness5/5

The set covers the full workflow: discover factors, resolve amiguous plain-language queries, look them up individually or in batch, perform domain-relevant calculations, and even explain why a factor is absent. The main GHG scopes are covered by dedicated calculators while the generic calculate_activity fills gaps for any other factor data.

Resources

Need Help?