Skip to main content
Glama

industrial-inspection-q-115700

industrial-inspection-q-115700

industrial-inspection-q-115700 — 把工业设备类型和巡检场景转成结构化巡检提问清单,覆盖机械、电气、仪表三大类。单次调用输出不超过 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-115700"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPayload for industrial-inspection-q-115700

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-115700"
    • 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?

The description adds value beyond the annotations by disclosing the 12-item output cap, the required batching workaround, the three coverage domains, and a cost of 5 MESH per call. The annotations already declare the side-effect profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and nothing here contradicts them. However, it says nothing about what the returned items look like, whether batching preserves context, or what happens with unrecognized equipment types — with an open-world tool that gap matters.

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 sentences plus a cost tag; the purpose leads, the operational constraint (12-item cap) follows. The appended '(5 MESH/call, a tool · business)' is metadata but is genuinely useful cost information rather than filler. Minor waste from repeating the opaque tool name as the opening token.

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 carries the burden of describing the return value, and it does reasonably well: a structured checklist, three equipment domains, maximum 12 items. For a single-object-payload generator this is close to complete. It could still say more about item structure (question format, per-category counts) and output language, which is unstated despite a Chinese description.

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%: both nested required fields (equipment_type, scenario) carry their own descriptions with examples such as pump, motor, boiler and routine patrol, fault diagnosis, acceptance check. The description confirms both inputs drive the output but adds no format, vocabulary, or granularity guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a concrete transformation: equipment type + inspection scenario → structured inspection question checklist, covering mechanical, electrical, and instrumentation categories. That is a specific verb-and-resource statement an agent can act on. It does not, however, distinguish this tool from the many near-identically named industrial-inspection-q-* siblings, so an agent cannot tell which variant to pick from the description alone.

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 implied by the input framing (supply equipment type and scenario to get a checklist), and one real constraint is given: output is capped at 12 check items, so larger scopes must be split into batches. There is no explicit when-to-use vs. when-not guidance and no naming of an alternative among the sibling inspection tools.

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.