Skip to main content
Glama

nws_public_witnessing_schedule

Retrieve cached public witnessing locations, shifts, and positions for a specified date to review scheduled coverage.

Instructions

Show cached public-witnessing locations, shifts, and positions for a date.

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": {
      "date": "<date>"
    },
    "name": "nws_public_witnessing_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one meaningful trait — that results come from a cache, implying possible staleness — which is real value beyond the schema. However it says nothing about authentication needs, refresh behavior, or whether the cache can be bypassed, which matters for a schedule-viewing tool.

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?

A single front-loaded sentence with no filler; the resource list and the date scoping are stated up front. It is appropriately sized, though the terseness contributes to the missing parameter format detail.

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?

An output schema exists, so return values need not be explained, and the read-only nature is self-evident from 'Show'. What is missing is the date format and any guidance on cache staleness versus live data — gaps an agent would have to resolve by trial and error.

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% for the single 'date' parameter, so the description must compensate and it does not. It only restates 'for a date' without specifying format (ISO YYYY-MM-DD?), timezone, or whether past/future dates behave differently. This leaves the agent guessing at the one input it must supply.

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 gives a concrete verb (Show) plus a specific resource set — cached public-witnessing locations, shifts, and positions — scoped to a date. An agent can tell this is the read/view operation rather than the many preview/commit/cancel mutation siblings. It stops short of naming a specific sibling it differs from, so it is clear but not fully differentiated.

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 statement of when to use this versus nws_public_witnessing_locations_utilization, nws_public_witnessing_publishers_reservations, or the preview_* variants. The only contextual hint is the word 'cached', with no explanation of how that should influence tool choice. No prerequisites or exclusions are given.

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

Deploy Server

Other Tools