Skip to main content
Glama

industrial-inspection-q-115759

industrial-inspection-q-115759

industrial-inspection-q-115759 — 把工业设备类型和巡检场景转成结构化巡检提问清单,覆盖机械、电气、仪表三大类。单次调用输出不超过 12 个检查项,超出请分批。 (5 MESH/call, a tool · business)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "industrial-inspection-q-115759"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPayload for industrial-inspection-q-115759

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / input / additionalProperties
      Added value: +true
    • changedInput schema / properties / input / description
      Previous value: -"Capability-specific payload, e.g. agent-brain: {think:'...'}; agent-memory: {action:'store'|'recall', content|query}"New value: +"Payload for industrial-inspection-q-115759"
    • addedInput schema / properties / input / properties
      Added value: +{
      +  "equipment_type": {
      +    "description": "REQUIRED — equipment type (industrial equipment type, e.g. pump, motor, boiler).",
      +    "type": "string"
      +  },
      +  "scenario": {
      +    "description": "REQUIRED — inspection scenario (routine patrol, fault diagnosis, acceptance check...).",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / input / required
      Added value: +[
      +  "equipment_type",
      +  "scenario"
      +]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare openWorldHint=true and readOnlyHint=false, so the agent knows this is not a purely local read operation; the description does not contradict that. It adds genuine behavioral context that annotations do not cover: the 12-item output cap, the batching advice, and a cost figure for each call. It says nothing about determinism, latency, or error behavior, which matters for a non-idempotent generation tool.

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?

Two short sentences that lead with the purpose and end with the operational constraint, with no filler. The only waste is the echoed tool identifier at the start and the trailing cost/business tag, which add little for an agent already reading structured metadata.

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?

There is no output schema, so the description carries the return-shape burden, and it does say the output is a structured checklist of at most 12 items spanning three equipment domains. For a one-parameter generation tool this is close to sufficient; only the absence of alternatives guidance and error behavior keeps it from a 5.

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 coverage is 100%, and the schema already documents both nested fields as required and gives examples (pump, motor, boiler; routine patrol, fault diagnosis, acceptance check). The description only restates the two inputs at a high level, adding no format, granularity, or free-text conventions beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific transformation: it converts equipment type plus inspection scenario into a structured inspection question checklist, and names the covered domains (mechanical, electrical, instrumentation). This is far more informative than the title. It does not distinguish itself from the many similarly named sibling tools, which is the main gap.

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?

The description gives one practical usage rule: a single call returns at most 12 checklist items, so larger scopes must be batched. It gives no explicit when-to-use or when-not-to-use guidance and names no alternative tool among the near-identical siblings, leaving selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.