Skip to main content
Glama
Sign In

Osmanth Agent Hub

by com.osmanth
OverviewDiscussionsAdmin

hub_postal

Read-only

Look up one postal code at PostalCodeCheck. Their terms and API page, read on 2026-11-08, allow personal and commercial use of the keyless tier and cap it at 100 requests a day per IP. This hub caches results and keeps fresh calls under that cap for the whole service. Does not spend points and does not accept a URL. If you supply fields, the hub returns privacy_consent_required until the controller has accepted the current privacy version. Do not invent that acceptance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>",
      "code": "<code>"
    },
    "name": "hub_postal"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations cover the read-only and open-world profile, and the description adds genuinely new behavior: a documented upstream rate cap, caching semantics, that no points are consumed, and the privacy_consent_required response path with the warning not to fabricate consent. It stops short of describing what a successful result contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and every sentence carries information, but phrasing is awkward ('Their terms and API page, read on 2026-11-08') and the licensing/terms aside is dense relative to its operational value.

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?

No output schema exists, so the description should sketch return shape; it only hints at a privacy_consent_required outcome and says nothing about the success payload (place name, region, coordinates). For a 2-required-param lookup with zero schema descriptions, this leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden and it does not: nothing explains that 'country' is an ISO-3166 alpha-2 code or that 'code' is a 2-12 character postal string. Worse, 'If you supply fields' is misleading because both parameters are required, so fields are always supplied.

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?

Starts with a specific verb+resource: 'Look up one postal code at PostalCodeCheck'. The single-record scope is clear and the negative constraint 'does not accept a URL' helps distinguish it from URL-based tools. It never names or contrasts with hub_postal-backup, so sibling differentiation is left implicit.

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?

Supplies useful operating context (100 requests/day per IP cap, hub-level caching, 'does not spend points'), which implicitly tells an agent when this is cheap to call. However, there is no explicit when-to-use/when-not guidance and no mention of hub_postal-backup as the fallback when the cap is hit.

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

All Osmanth Agent Hub 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