Skip to main content
Glama

Expand vulgar fractions

bpj_map_typographic_fractions
Read-onlyIdempotent

Expand Unicode vulgar fractions into numerator, slash and denominator 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_map_typographic_fractions"
  }
}

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds the output form (numerator/slash/denominator), which matters because there is no output schema, but it omits what happens to non-fraction characters, mixed text, or edge cases like 1/2 in a longer string.

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 no filler; the transformation and its result are stated together, so nothing needs to be skimmed.

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 one-parameter, closed-world, deterministic mapping tool with full annotations and no output schema, the description covers input intent and output shape adequately. The remaining gap is passthrough behavior for text without vulgar fractions, which an agent would want to know before sending arbitrary strings.

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 one parameter with 0% schema description coverage; the schema only gives a title ('Source text') and a maxLength of 6000. The description implies the input is the text holding the fractions but adds nothing about format, character limits, or whether the whole string or only matched spans are transformed.

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?

Names a precise verb and resource ('Expand Unicode vulgar fractions') and even states the output shape (numerator, slash, denominator text), so an agent knows exactly what transformation happens. It does not need to differentiate from siblings because the listed siblings are unrelated utility calculators, but it also makes no effort to position itself against any nearby text tool.

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?

There is no explicit 'use this when' or 'do not use this when' statement, and no named alternative. Usage is only implied by the narrowness of the stated transform, which is enough for an agent to infer the trigger condition but leaves ambiguity for mixed or partially-fractional 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.