Skip to main content
Glama

industrial-inspection-q-115422

industrial-inspection-q-115422

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

Input Schema

NameRequiredDescriptionDefault
inputYesPayload for industrial-inspection-q-115422

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-115422"
    • 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.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, open-world, non-idempotent behavior. The description adds genuinely new operational facts: a hard cap of 12 output items per call and a cost of 5 MESH per call, both of which affect how an agent plans batching. It does not elaborate further on output format, but for a generation tool the capacity and cost disclosures are the substantive gaps it closes.

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, front-loaded with the core transformation, followed by the batching limit. The trailing '(5 MESH/call, a tool · business)' tag is metadata noise but small enough not to obscure the payload.

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: a structured question checklist capped at 12 items across three equipment domains. Combined with the cost and batching note, an agent has enough to call it correctly; only sibling differentiation is missing.

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%, with both nested fields (equipment_type, scenario) documented including examples, so the baseline is 3. The description corroborates that equipment type and inspection scenario are the inputs and adds the domain taxonomy (mechanical/electrical/instrumentation), but supplies no extra syntax or value guidance beyond the schema.

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 names a concrete verb and resource: it converts an equipment type plus inspection scenario into a structured inspection-question checklist, and it names the covered domains (mechanical, electrical, instrumentation). It is clear what the tool produces, though it offers no differentiation from the near-identical sibling tools (industrial-inspection-q-115026, -115241, etc.).

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?

It gives one real usage constraint: a single call returns at most 12 check items, and larger needs must be batched across calls. There is no guidance on when to prefer this tool over the similarly named siblings, nor any exclusion or prerequisite, so the when-to-use picture is only partially implied.

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.