Skip to main content
Glama
Sign In

Postcodes

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Validate Postcode

validate_postcode
Read-onlyIdempotent

Validate a UK postcode format (e.g., 'SW1A 1AA'). Returns whether it's valid and format details.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postcode": "SW1A 1AA"
    },
    "name": "validate_postcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesUK postcode to validate (e.g. "SW1A 1AA").

Output Schema

NameRequiredDescriptionDefault
validYesWhether the postcode is valid
postcodeYesThe UK postcode that was validated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "postcode": {
+      "description": "The UK postcode that was validated",
+      "type": "string"
+    },
+    "valid": {
+      "description": "Whether the postcode is valid",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "postcode",
+    "valid"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "postcode": "SW1A 1AA"
+  },
+  {
+    "postcode": "invalid"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent). The description adds that it returns validity and format details, which is useful but does not disclose limitations such as not checking real-world existence or handling of whitespace/case. No contradiction with annotations.

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, tightly worded sentence that immediately conveys the tool's purpose and output. No filler, front-loaded with the key action, and includes a concrete example.

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 simple single-parameter validator with rich annotations (readOnly, idempotent) and an output schema, the description provides enough context. It could optionally mention edge cases like case sensitivity or non-existence checks, but the tool's simplicity makes the description largely complete.

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 an example already provided. The description repeats the postcode example, adding no significant meaning beyond the schema. Baseline 3 is appropriate since the schema fully documents the parameter.

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?

The description uses the specific verb 'Validate' with a clear resource 'UK postcode format' and provides an example. It distinguishes from sibling tools like lookup_postcode, which focuses on retrieving data, and random_postcode, which generates postcodes.

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 for format validation but does not explicitly state when to use this tool over alternatives such as lookup_postcode or nearest_postcodes. No exclusions or alternative tool guidance is provided, leaving usage context implicit.

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

All Postcodes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources