Skip to main content
Glama

GPS second-of-week band

by io.github.sadri-dridi
OverviewDiscussionsAdmin

gps-sow

GPS second-of-week band

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

D1.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description does not mention that all parameters are optional, that it likely returns a time band, or that it is a read-only, non-destructive operation. The schema descriptions sometimes note 'discarded after the check', but those are schema-level and not summarized in the tool description. It provides almost no behavioral context.

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 extremely short (4 words), which is concise, but it is under-specified. It does not front-load any action or purpose. Every word should earn its place, but here they do not communicate the tool's function. It is under-descriptive rather than effectively concise.

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?

The tool has 10 parameters, an output schema is absent, and annotations are missing. The description does not explain how these parameters are used or what the output looks like. For a tool with such a large parameter surface, the description is completely inadequate. An agent cannot determine why it would call this tool or what result to expect.

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?

The description provides no parameter semantics beyond what the schema already details. Schema description coverage is 100%, so the schema does most of the work. However, the description offers no high-level explanation of which parameter to use or how they relate to the 'GPS second-of-week band'. For example, 'zone' might be relevant but is not highlighted. The description adds essentially no value over the schema.

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

Purpose1/5

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

The description 'GPS second-of-week band' is an unexplained name fragment. It does not state a verb or resource, nor does it clarify what the tool does with the input parameters. It is closer to a tautology of the tool name 'gps-sow' (GPS second-of-week) and offers no actionable meaning for an agent.

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?

There is no explicit guidance on when to use this tool versus siblings. The description only hints at a 'GPS second-of-week band' but does not explain what condition should trigger its use or when to prefer another tool. Among 30 siblings, the only weak link is the 'geo-hint' and 'timezone' tools, but no clear distinction is made.

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

All GPS second-of-week band 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