Skip to main content
Glama

industrial-inspection-q-115516

industrial-inspection-q-115516

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

Input Schema

NameRequiredDescriptionDefault
inputYesPayload for industrial-inspection-q-115516

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-115516"
    • 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 readOnly=false, openWorld=true, idempotent=false, destructive=false, so the safety profile is largely covered. The description adds genuinely new behavioral facts: the 12-item output ceiling, the batching workaround, and the per-call cost of 5 MESH. It still does not say what a checklist item looks like or whether exceeding the cap truncates silently.

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?

The substantive content is two tight sentences: purpose plus scope, then the output cap and batching rule. The only waste is the opening repetition of the opaque tool name and the appended pricing parenthetical, but neither obscures the front-loaded purpose statement.

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?

For a single-parameter generator with no output schema and full schema coverage, the description supplies what is missing: category coverage, the output size limit, and the batching remedy. The main residual gap is the shape of a returned check item and whether batching means multiple calls or a paging parameter.

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 sub-fields (equipment_type, scenario) documented including examples such as pump, motor, boiler and routine patrol, fault diagnosis, acceptance check. The description restates the two inputs at a high level but adds no format or vocabulary constraints beyond the schema, so the baseline 3 applies.

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 specific verb and transformation: turning equipment type plus inspection scenario into a structured inspection question checklist, scoped to mechanical, electrical, and instrumentation categories. An agent knows what comes out. It is not differentiated from the many similarly named industrial-inspection-q-* siblings, but the core purpose is unambiguous.

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?

There is a concrete operating constraint — no more than 12 check items per call, batch when larger — which tells the agent how to call it. However, there is no guidance on when to prefer this over the sibling questionnaire tools, and no statement of prerequisites or what happens if a scenario is outside the three covered categories.

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.