normalize-decimal
Normalize common US/EU decimal representations to a dot-decimal string. Ambiguous single separators followed by three digits are flagged.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes |
Internet Janitor
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses a non-obvious rule for ambiguous single separators followed by three digits, but uses the vague term 'flagged' without explaining the resulting behavior (error, marker, or special output). With no annotations, this ambiguity is a notable gap in transparency.
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?
Two sentences with zero filler: the first sentence front-loads the core transformation, and the second adds a relevant edge-case behavior. Every clause contributes meaning.
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?
The description covers the main operation and one edge case, but it leaves unresolved the meaning of 'flagged' and does not describe return format or error behavior. Since there is no output schema and no annotations, these omissions limit the agent's ability to handle all outcomes correctly.
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?
With 0% schema description coverage, the description compensates by indicating the input is a US/EU decimal representation and that normalization applies to it. It does not explicitly name the parameter or provide examples, but the semantic intent is inferable and much richer than the bare schema.
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 ('Normalize') and resource ('common US/EU decimal representations') with a defined output ('dot-decimal string'). This clearly differentiates it from siblings like normalize-boolean and normalize-whitespace, which target different data types.
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 description implies usage: when decimal strings need conversion to dot-decimal format. However, it provides no explicit mention of when to use this tool over alternatives or any exclusions, leaving the agent to infer context.
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.
TDQS
A3.9/5.0
Disambiguation5/5
Each tool targets a clearly separate concern: delimiter detection, three distinct normalization tasks, and filename sanitization. There is no realistic confusion between them, even though several share a normalize- prefix.
Naming Consistency4/5
Most tools follow a verb-noun kebab-case pattern such as detect-delimiter and normalize-whitespace. safe-filename slightly deviates because it is adjective-noun rather than a command, but the overall convention is still mostly predictable.
Tool Count5/5
Five tools is a compact, well-scoped set for a data-cleaning utility server. Each tool has a clear purpose and none feel redundant or excessive.
Completeness3/5
The covered tasks are useful and coherent, but the 'Internet Janitor' domain implies a broader cleaning toolkit. Common janitorial operations like normalizing line endings, handling encodings, or normalizing dates are missing, leaving noticeable gaps despite the solid core.