Skip to main content
Glama
sebastienrousseau

structured-address-fix-mcp

Classify a postal address

classify_address
Read-onlyIdempotent

Quickly classify a postal address as structured, hybrid, or unstructured to decide if remediation is needed for compliance.

Instructions

Classify a postal address as structured, hybrid, or unstructured.

Use this for a quick shape check before deciding whether to remediate.
For the specific compliance findings under a policy, use
``assess_address`` instead.

Args:
    address: The postal address to classify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesAn ISO 20022 postal address as a JSON object using canonical field names, e.g. {'street_name': 'Downing St', 'building_number': '10', 'post_code': 'SW1A 2AA', 'town_name': 'London', 'country': 'GB'} or {'address_lines': ['10 Downing St', 'London SW1A 2AA'], 'country': 'GB'}.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint. The description adds minimal new context ('quick shape check'), but does not contradict annotations. Since annotations are comprehensive, a score of 3 is appropriate.

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?

Description is short and front-loaded with the main purpose. It includes a clear usage guide and an Args section. Every sentence is essential; no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool (one parameter, classification output), the description fully covers what an agent needs: purpose, usage context, and alternative. Output schema exists but is not required to be explained.

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?

Schema description coverage is 100% with a detailed explanation of the 'address' parameter. The description simply restates 'The postal address to classify,' adding no new meaning. Baseline of 3 applies.

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?

Description clearly states 'Classify a postal address as structured, hybrid, or unstructured.' The verb 'classify' and the specific categories make the purpose precise. It also distinguishes from sibling assess_address by indicating a quick shape check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this for a quick shape check before deciding whether to remediate.' and contrasts with 'For specific compliance findings, use assess_address instead.' This provides clear when-to-use and an alternative, meeting the highest standards.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/structured-address-fix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server