Skip to main content
Glama

Format Roman numerals

bpj_discrete_roman_numeral
Read-onlyIdempotent

Format an integer from 1 through 3999 in canonical subtractive Roman notation.

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": {
      "integer": "<integer>"
    },
    "name": "bpj_discrete_roman_numeral"
  }
}

Input Schema

NameRequiredDescriptionDefault
integerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one real behavioral fact not in the annotations: output uses canonical subtractive notation (e.g. IV rather than IIII). It does not state error behavior for out-of-range values.

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 action and constrained by range and notation convention. No filler or redundant wording.

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 pure single-argument formatter with no output schema, the description conveys both accepted input domain and output notation style, which is what an agent needs. A short example or explicit out-of-range behavior would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the meaning, and it does: the single parameter is the integer to convert, valid from 1 to 3999. This largely restates the schema's minimum/maximum, so it adds clarity rather than new information, but for a one-parameter tool that is sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Format") and resource ("an integer ... in ... Roman notation") plus the output convention ("canonical subtractive"). The purpose is fully determinable from the description alone; the sibling tools are unrelated discrete-math functions, so no disambiguation is required.

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?

The domain constraint (1 through 3999) implicitly tells the agent when the tool is applicable and when it is not, but there is no explicit when-to-use guidance, no mention of alternatives, and no note on what happens for out-of-range input.

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.