Skip to main content
Glama

Mixed number styles

bpj_numeric_style_mix
Read-onlyIdempotent

Find values from zero to ten appearing both as digits and English number words.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so safety is covered externally. The description adds essentially no behavior beyond that: it doesn't say whether "both" means both forms must occur in the same document or merely that either form may be returned, how matches are reported, or whether case/formatting variants of the words count.

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?

One sentence, front-loaded with the detectable pattern, with no filler or redundant restatement of the tool name. Everything present earns its place.

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 one-parameter, read-only tool with annotations covering safety and no output schema, the description is close to sufficient but leaves a genuine ambiguity: whether a match requires both digit and word forms in the same input, and what a returned "finding" looks like. A single clarifying clause on the match rule would make it complete.

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?

There is a single parameter ("text", maxLength 6000) and the schema carries only a title, no real description (0% coverage). The description's "appearing" strongly implies the parameter is the text to be scanned, which is a modest assist, but it says nothing about length limits, encoding, or how much text can realistically be analyzed in one call.

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 ("Find") and a specific object ("values from zero to ten appearing both as digits and English number words"), which is concrete enough for an agent to predict the output. It does not, however, distinguish itself from plausible siblings such as bpj_number_text_lines, bpj_dq_mixed_types, or bpj_mixed_english_spellings, so the agent must infer which of these overlapping text-inspection tools to pick.

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 explicit when-to-use statement, no prerequisites, and no named alternative. The agent must guess the selection criteria between this and the several sibling tools that also scan text for number/word mixing; nothing states the condition that makes this tool the right choice.

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.