Skip to main content
Glama

XML 1.0 character check

bpj_xml_character_check
Read-onlyIdempotent

Locate scalar values disallowed by the XML 1.0 Char production.

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": {
      "text": "<text>"
    },
    "name": "bpj_xml_character_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered and the description needn't repeat it. The description does add value by pinning the check to a named external specification (XML 1.0 Char production), which tells the agent the exact rule being enforced. However, it says nothing about what "locate" yields (offsets, offending code points, a count) or how truncation at the schema's 6000-character limit affects the result.

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?

A single sentence with no filler, and the core concept (disallowed characters, XML 1.0 basis) is front-loaded. The terseness is efficient rather than padded, though it is thin enough that the same budget could have carried one clause about the input or the return value.

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 simple, side-effect-free scanner with annotations in place and a one-field schema, this is close to adequate. The gap is that no output schema exists, so the description is the only place that could explain the shape of the result, and it does not — leaving the agent unable to anticipate whether it receives positions, values, or a boolean.

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?

With a single parameter and 0% schema description coverage, the schema offers only the title "Source text" and a maxLength constraint. The description does not clarify that `text` is the string to be scanned, nor does it warn that input beyond 6000 characters is rejected rather than partially scanned. Baseline for a one-parameter tool is a 3, and the description does not lift it above that.

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 pairs a specific verb ("Locate") with a precisely bounded resource ("scalar values disallowed by the XML 1.0 Char production"), which is far more informative than a generic "validate XML" claim. It is clear what class of defect is being detected, though it never states that the scan operates on the caller-supplied `text` parameter, so the object of the search is left implicit.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool versus the many other bpj_* check tools, and no stated preconditions, exclusions, or follow-up actions. The agent must infer from the name alone that this is a pre-serialization sanity check on a string it already holds.

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.