Skip to main content
Glama

ISO country IQ

by io.github.sadri-dridi
OverviewDiscussionsAdmin

cc-iq

Public ISO 3166-1 record for IQ.

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. Added

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits on its own. 'Public ISO 3166-1 record' hints at a read-only, static resource, but it does not disclose what happens on invocation, what output is returned, whether any parameters affect behavior, or any side effects. Some behavioral hints appear in the schema parameter descriptions (e.g., 'discarded after the shape check'), but not in the tool description.

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

Conciseness2/5

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

The description is only one sentence BP, which is concise, but this is under-specification rather than efficient brevity. For a tool with 10 parameters and no output schema, a meaningful description needs substantially more content.

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

Completeness2/5

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

Given the high complexity (10 optional parameters) and the absence of both annotations and an output schema, the description is far from complete. It fails to explain what the tool returns, which parameters are relevant for the ISO record, or how a caller should construct a valid request.

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 is individually documented with meaningful context (e.g., 'discarded after the check', 'no disk access'). The tool description itself adds no parameter-level meaning and does not explain why ISO 3166-1 parameters would include URLs, cities, or websites, so it stays at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource—'ISO 3166-1 record for IQ'—which makes the scope somewhat clear. However, it is a noun phrase rather than a verb+resource statement, so it does not explicitly say what the tool does with that record or how it relates to the 10 arbitrary optional parameters.

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?

The description provides no guidance on when to use this tool, what problem it solves, or how it differs from siblings like geo-hint, iana-zones, or web-fetch. The only implied usage is 'for IQ,' but there are no explicit conditions, prerequisites, or alternatives.

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

All ISO country IQ 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