Skip to main content
Glama

Australian postcode digit shape, value discarded

by io.github.sadri-dridi
OverviewDiscussionsAdmin

au-postcode

Australian postcode digit shape, value discarded

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoGit ref name; discarded after the shape check
urlNoHTTPS URL to normalize or cite
cityNoCity name for a public weather hint; discarded after the call
feedNoPublic RSS or Atom URL; titles discarded
hostNoPublic hostname
jsonNoJSON text to validate; discarded after the check
pathNoFile path to check; no disk access
zoneNoIANA timezone name
queryNoSearch text; discarded after the length check
websiteNoPublic https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / website
      Added value: +{
+  "description": "Public https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.",
+  "type": "string"
+}
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

The phrase 'value discarded' discloses that the input value is not retained and that actual postcode validity is not checked, which is useful behavioral context. However, there are no annotations, no output description, and no mention of side effects, failure behavior, or what the tool returns, leaving a substantial transparency gap.

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?

The description is extremely concise at six words and front-loads the core purpose ('Australian postcode digit shape'). It contains no filler, though the awkward phrase 'digit shape' and lack of context prevent a perfect score.

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

Completeness1/5

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

With 10 optional parameters, no output schema, no annotations, and many sibling shape tools, this description is far too sparse. It does not explain what the tool returns, how success or failure is indicated, which parameter to populate, or why an agent would choose it over similar tools.

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% and each parameter has a description, so the baseline is 3. The tool description adds no parameter-level meaning and, notably, does not indicate which of the ten parameters should contain the postcode value, which weakens its contribution.

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?

The description states the tool checks the digit shape of Australian postcodes and discards the value, making the core operation clear from the resource type. It distinguishes itself from sibling shape tools by naming a specific domain (Australian postcodes), though it lacks an explicit verb like 'validate' or 'check'.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus sibling tools such as domain-shape, github-repo-shape, or jira-key-shape. There is no stated condition, alternative, or exclusion, so the agent must infer when this tool applies.

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

All Australian postcode digit shape, value discarded 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