Skip to main content
Glama
Sign In

RoboParts 机器人零部件兼容性

by cc.roboparts
OverviewDiscussionsAdmin

explain_unknown

结构化解释「为什么某次判定是 unknown」。三种模式：① component_id + category → 返回该实体的 evidence_gaps / null 字段清单；② verdict_id → 反查当前请求内的判定（hosted 端点无跨请求会话，仅回当前请求）；③ 无参 → 返回全库 unknown 覆盖率摘要。★ 口径纪律：字段级扫描 ≠ 因果归因（后者属 gap_classification 研究层）。只读、免鉴权。

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

Input Schema

NameRequiredDescriptionDefault
categoryNo品类：actuators / sensors / chips / interfaces / protocols / llms / platforms / flexible_actuators / robot_ai_models / data_acquisition / connectors / integrated_joints / reducers / controllers / grippers / structural / cables / power / pcb / bionic_mechanisms
max_gapsNo最多返回多少条缺口
verdict_idNo判定 verdict_id（hosted 端点仅当前请求内可查）
component_idNo组件 ID，如 ACT-001、SENS-001

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose important behavior: read-only, auth-free, current-request-only verdict lookup, and distinct return content per mode. It stops short of describing exact response structure or edge-case behavior, so it is strong but not exhaustive.

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?

The description is compact and front-loaded, with the three modes clearly separated and the scope-discipline caveat called out at the end. Every sentence contributes operational information.

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?

Given three distinct modes, no output schema, and no annotations, the description supplies enough context to choose a mode and understand what each mode returns at a high level. The session limitation and read-only/auth-free guarantees are especially relevant for correct invocation.

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?

Schema coverage is 100%, so the schema already documents all four parameters. The description adds useful meaning by explaining how component_id + category select mode 1 and how verdict_id selects current-request lookup, though max_gaps is not discussed in prose.

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 specific verb and resource: structurally explain why a verdict is unknown. It also enumerates three concrete modes, making the tool's scope distinguishable from a causal-attribution or research-layer operation.

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?

Usage is explicitly tied to parameter combinations: component_id + category for entity-level gaps, verdict_id for current-request lookup, and no arguments for the global coverage summary. The hosted-endpoint session limitation is also stated, removing ambiguity about when mode 2 applies.

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

All RoboParts 机器人零部件兼容性 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