Skip to main content
Glama

match_labs

Scores and ranks testing labs by capability keyword, region, and device description, returning matched capabilities and contact details for orthopedic device testing.

Instructions

按能力关键词 / 地区 / 器械描述给检测机构打分排序。例:scope_keyword='力学疲劳'。返回命中能力项与联系方式;示例数据仅 3 家机构。

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数,默认 5
deviceNo器械描述,如 接骨板
regionNo地区码,如 CN-JS
scope_keywordNo能力关键词,如 力学疲劳、生物相容性

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the response contents ('命中能力项与联系方式') and an important limitation ('示例数据仅 3 家机构'), which prevents the agent from over-trusting sparse results, but it says nothing about read-only semantics, pagination, or how ties are ranked.

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?

Three short clauses, front-loaded with the core action before the example and the return/limitation note. No filler sentences, though the inline example partially duplicates the schema's own examples.

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 correctly describes what comes back (matched capability items and contact details) and warns that the sample corpus is only three labs. For a zero-required-parameter search tool this is close to sufficient; only ranking/combination semantics remain unspecified.

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 each of the four parameters is already documented, including the example values the description repeats. The description adds only the framing that keyword/region/device jointly drive scoring, without explaining whether criteria are ANDed, weighted, or optional in combination.

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 gives a concrete verb phrase ('给检测机构打分排序') plus the resource (testing labs) and the three ranking criteria (capability keyword / region / device description), so an agent knows exactly what the tool produces. It does not name or distinguish against any sibling, but no sibling in the catalog overlaps with lab matching, so confusion risk is low.

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?

Usage is only implied: the embedded example (scope_keyword='力学疲劳') shows how to invoke it, but there is no statement of when to prefer this over other lookup tools, no preconditions, and no note on behavior when multiple criteria are supplied.

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