Skip to main content
Glama

Unix day-of-year from seconds

by io.github.sadri-dridi
OverviewDiscussionsAdmin

unix-doy

Unix day-of-year from seconds

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.3/5.0
Behavior1/5

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

With no annotations, the description must carry the full behavioral burden, and it only states a formula. It does not say whether the tool reads current time, which parameters are consulted, what output format is returned, or whether any side effects occur. The per-parameter 'discarded' notes live in the schema, not in the tool description, and the description adds 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 short, but it is under-specified rather than concise. It front-loads no actionable information and omits the essential relation between the described computation and the actual parameters, so brevity does not help the agent.

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?

For a 10-parameter, zero-required tool with no output schema and no annotations, a one-sentence formula leaves out nearly everything needed for correct invocation: input selection, output shape, error behavior, and side-effect profile. It is not a usable definition.

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 schema documents each parameter individually, so the normal baseline is 3, but the description's central input ('seconds') does not correspond to any parameter. The agent is left guessing whether to pass zone, query, ref, or nothing; the description adds no meaning beyond the schema and actually creates a semantic mismatch.

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 'Unix day-of-year from seconds' essentially restates the tool name and gives no mapping to any of the 10 input parameters; none of them represents seconds. It also fails to distinguish the tool from related date/time siblings like utc-time, timezone, or calc-eval. An agent cannot tell what input would produce the result.

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

Usage Guidelines1/5

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

There is no guidance about when to call unix-doy versus alternatives, no prerequisite, and no hint about which of the many optional parameters should be supplied. The sibling list contains several plausible date/time tools, but the description does not route the agent to or away from any of them.

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

All Unix day-of-year from seconds 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