Skip to main content
Glama
sebastienrousseau

structured-address-fix-mcp

Split street and building

split_street_and_building
Read-onlyIdempotent

Parses a free-text street line into street name, building number, and sub-building, handling leading or trailing number formats. Returns the full line as street name when no building number is present.

Instructions

Split a street line into street name, building, and sub-building.

Handles the leading-number convention (US/UK: ``10 Downing Street``),
the trailing-number convention (much of continental Europe: ``Rue de
Rivoli 12``), and an optional sub-building marker (``Flat 2``, ``Apt
3B``, ``Suite 400``). When no building number is present the whole line
is returned as ``street_name`` (never an error).

Args:
    street_line: The free-text street line to split.

Returns ``{"street_name", "building_number", "sub_building"}`` with
``building_number`` / ``sub_building`` set to ``null`` when absent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
street_lineYesA single free-text street line, e.g. '10 Downing Street', 'Rue de Rivoli 12', or 'Flat 2, 221B Baker Street'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses concrete parsing behavior: support for both numbering conventions, optional sub-building markers, null outputs when absent, and never returning an error for a missing building number. This is exactly the kind of non-obvious behavior an agent needs.

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?

The description is compact, front-loaded with the operation, and uses a clear Args/Returns structure. Every sentence adds either input semantics, output semantics, or edge-case behavior.

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?

For a single-parameter pure function with full schema coverage and annotations, the description covers input, output shape, null conventions, and edge cases. The existing output schema also covers return values, so nothing necessary is missing.

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 coverage is 100% and the schema already names the parameter with examples. The description's Args line adds little beyond restating that street_line is free-text to split, so the 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?

States a specific verb ('split'), resource ('street line'), and the three output components. It clearly distinguishes itself from sibling address tools by focusing on splitting into street_name, building_number, and sub_building.

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

Usage Guidelines4/5

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

The description gives clear context for when it applies by naming the two numbering conventions and the no-building-number case, so an agent can recognize the right input shape. It does not explicitly compare against siblings such as parse_address_libpostal, but no misleading guidance is given.

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

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