Skip to main content
Glama

Join print hyphenation

bpj_join_print_hyphenation
Read-onlyIdempotent

Join a hyphen and a line break between Latin letters when cleaning extracted print text.

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_join_print_hyphenation"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds the meaningful behavioral constraint that the join applies only when the hyphen sits between Latin letters, but it does not say what happens to non-matching text or how multiple consecutive hyphens/breaks are handled.

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

Conciseness5/5

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

A single front-loaded sentence with the action first and the qualifying condition second. Every clause earns its place; nothing is repeated from the schema or annotations.

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 simple deterministic string transform with one required parameter, an output schema absent, and full annotation coverage, the description gives enough to call it correctly. Only edge-case behavior (repeated hyphens, non-matching input passthrough) is left unstated.

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 0% for the single 'text' parameter, so the description must carry the meaning; it only implies the input is extracted print text. The parameter is self-evident from its name and required status, so the gap is minor, but no format, size, or edge-case guidance is added beyond the schema's maxLength.

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?

States a specific verb ('Join') and a precise resource ('a hyphen and a line break between Latin letters'), plus the domain of application ('extracted print text'). An agent can tell this is a de-hyphenation normalizer rather than a generic join, though it does not explicitly contrast itself with similarly named print-oriented siblings.

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?

'when cleaning extracted print text' supplies an implied usage context, and 'between Latin letters' implicitly excludes non-Latin scripts and mid-word hyphens. There is no explicit when-not guidance or named alternative for related cleanup steps, so the agent must infer the workflow placement.

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.