Skip to main content
Glama

Nalvorn Checks

ru_text_normalize

Read-only

Normalise Russian text (yo, quotes, dashes, spaces) and return metrics Free of charge.

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": "ru_text_normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to normalise (Russian punctuation and spacing)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, non-mutating call. The description adds real value by naming the four transformation categories and noting that metrics are returned, but says nothing about determinism, idempotency, or what the metrics are. 'Free of charge' is a cost note that adds marginal behavioral context.

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?

One compact sentence, front-loaded with the action and resource, and the parenthetical is efficient. The trailing 'Free of charge' is a marketing artifact that does not help an agent decide or invoke and could be dropped.

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 utility this is close to adequate, but the promised 'metrics' return value is never described and there is no output schema to fall back on, so the agent cannot anticipate the response shape. Non-Russian input behavior and any size constraints are also 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?

There is a single parameter and schema coverage is 100%, so the schema already carries the burden of documenting 'text'. The description's enumeration of normalised features (yo, quotes, dashes, spaces) adds meaning about what the transformation does to the input, but not about input format, size limits, or handling of mixed-language text.

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?

Specific verb ('Normalise') plus resource ('Russian text'), with a parenthetical enumerating exactly what is transformed (yo, quotes, dashes, spaces) and the fact that metrics are returned. Siblings are unrelated verification tools, so no differentiation is needed; the only shortfall is that the scope of 'normalise' is described by examples rather than defined.

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?

Usage is implied by the domain qualifier 'Russian text' and the transformation list, which tells an agent this is a pre-processing/cleanup utility. There is no explicit when-to-use statement, no exclusions (e.g. what happens to non-Russian input), and no named alternative.

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.

Resources