Skip to main content
Glama

Trustbase Lab · Trusted Data Infrastructure for the AI Era

by com.trustbaselab
OverviewDiscussionsAdmin

query_domain_benchmarks

query_domain_benchmarks
Read-onlyIdempotent

Purpose: search the cross-domain benchmark layer - the same verifiable-anchor methodology we apply to rCB, extended to other domains (carbon footprint & markets / telecom & space / health & nutrition / new energy & batteries / compute & energy). Records are policy milestones, official limit values, standards status and dated price snapshots, each with an issuer, an as-of date, a confidence grade and a source_url. Guidelines: filter by domain (carbon / telecom / health / energy / compute), region, category or confidence; every record is meant to be citable - pair with get_domain_benchmark by ID for the full record including the source link. Limits: anchor facts only - no price forecasts (carbon prices are dated snapshots, not live quotes), no medical or dosing advice, no diagnosis; the domain taxonomy is ours, not the issuing body's. Ex: query_domain_benchmarks(domain='carbon'), query_domain_benchmarks(keyword='CBAM'), query_domain_benchmarks(domain='health', confidence='A', language='en'), query_domain_benchmarks(domain='compute').

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限（默认 20，最大 100）
domainNo领域过滤：carbon=碳足迹·碳市场 / telecom=通信·空间 / health=健康·营养 / energy=新能源·电池 / compute=算力·能源（可留空取全部）
offsetNo起始偏移，默认 0；返回体 has_more=true 时用 next_cursor 作为下一页 offset
regionNo地区/组织过滤，如 '国际'、'欧盟'、'中国'
keywordNo关键词模糊匹配，如 'CBAM'、'3GPP'、'游离糖'、'碳市场'
categoryNo类别过滤，如 '时间节点'、'碳价快照'、'核算标准'、'膳食摄入限值'
languageNo输出语言zh
verifiedNotrue=只看 A 级已核实条目
confidenceNo置信度：A=官方一手来源核实, B=权威二手来源, C=待核实
response_formatNo输出格式：markdown=人类阅读, json=Agent 处理友好markdown

Output Schema

NameRequiredDescriptionDefault
textYesHuman-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "起始偏移，默认 0；返回体 has_more=true 时用 next_cursor 作为下一页 offset",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"领域过滤：carbon=碳足迹·碳市场 / telecom=通信·空间 / health=健康·营养（可留空取全部）"New value: +"领域过滤：carbon=碳足迹·碳市场 / telecom=通信·空间 / health=健康·营养 / energy=新能源·电池 / compute=算力·能源（可留空取全部）"
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description nonetheless adds real behavioral scope beyond them: records are 'anchor facts only', carbon prices are dated snapshots rather than live quotes, and the domain taxonomy is the tool's own rather than the issuing body's.

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?

Labelled sections (Purpose / Guidelines / Limits / Ex) make it front-loaded and skimmable, and the example calls are compact. The parenthetical domain lists add bulk but each element carries routing information, so little is wasted.

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?

An output schema exists, so return-values need no explanation, and annotations cover the safety profile. Between the coverage/limit filters, the cross-reference to get_domain_benchmark, and the explicit scope exclusions, an agent has everything needed to select and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage the baseline is 3; the description earns one extra point by demonstrating concrete parameter combinations ('Ex:' calls mixing domain, keyword, confidence and language) and by restating the semantic framing of domain values, which helps an agent build a valid call.

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?

States a specific verb+resource ('search the cross-domain benchmark layer') and enumerates exactly what a record is (policy milestones, limit values, standards status, dated price snapshots). It also distinguishes itself from the sibling get_domain_benchmark, which is the by-ID full-record lookup — an agent can route between them without opening either 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?

The Guidelines section names the filter axes (domain/region/category/confidence) and explicitly routes to 'get_domain_benchmark by ID for the full record including the source link'. The Limits section states when NOT to use it: no price forecasts, no medical/dosing advice, no diagnosis.

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

All Trustbase Lab · Trusted Data Infrastructure for the AI Era 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