Skip to main content
Glama

WritersLogic business agents

manual-applicability

Does this manual or procedure apply to this unit? — Checks whether a manual, service bulletin or procedure applies to a specific unit by comparing the scope the document declares (models, firmware or revision range, serial range, exclusions) with the unit's facts the caller supplies. Versions written as dotted digits (2.10.1) compare numerically per segment. For an agent about to follow a repair or configuration procedure. Applicable only when ever

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": {
      "applicability": "<applicability>",
      "unit": "<unit>"
    },
    "name": "manual-applicability"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesThe unit's facts: key is the field name.
excludesNoScope the document excludes: each entry that matches makes it inapplicable.
applicabilityYesScope the document declares: every entry must match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It explains the core comparison model (declared scope versus unit facts, with exclusions making the document inapplicable, and dotted-digit versions compared segment by segment), but it does not state the return value or explicitly confirm that the operation is read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening question and the following explanation are front-loaded and reasonably efficient. However, the truncated sentence fragment 'Applicable only when ever' is confusing dead weight and weakens the structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter check with a fully documented schema, the description adequately conveys what is compared and how exclusions work. The major gap is that there is no output schema and the description does not explain what the check returns, plus the trailing fragment leaves a usage condition unresolved.

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%, so the schema already documents all three parameters in detail, including min/max comparison semantics and exclusion behavior. The description adds some framing by naming model, firmware, revision, serial, and exclusions, but it does not add meaning beyond the schema's own parameter descriptions.

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 specific verb and resource: it checks whether a manual, service bulletin, or procedure applies to a specific unit, and explains that it does so by comparing declared scope with caller-supplied unit facts. This is much clearer than a tautology, but it does not explicitly differentiate the tool from any sibling, so it stops short of the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage context — 'For an agent about to follow a repair or configuration procedure' — which tells the agent when this check is relevant. It does not name alternatives or when-not conditions, and the trailing fragment 'Applicable only when ever' is incomplete guidance rather than a usable exclusion.

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.

Resources