Skip to main content
Glama

nws_public_witnessing_locations_utilization

Report public-witnessing shift capacity and reservations per location for a chosen YYYY-MM month and the three previous months from the local mirror.

Instructions

Report public-witnessing shift capacity and reservations per location.

Matches the desktop Locations Utilization report: the given YYYY-MM month (default: current) and the three previous months, from the local mirror.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nws_public_witnessing_locations_utilization"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results come from the local mirror and cover the given month plus the three previous months, but it does not state read-only behavior, authentication requirements, sync prerequisites, or pagination/response behavior.

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

Conciseness5/5

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

The description is two short sentences and is front-loaded with the tool's purpose. No sentence or clause is wasted.

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

Completeness4/5

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

Given one optional parameter and an existing output schema, the description covers purpose, time window, default behavior, and data source. The main remaining gap is that it does not mention whether a prior sync or authentication is required before the local-mirror report is accurate.

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

Parameters5/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 explain the sole parameter. It does so clearly by specifying the YYYY-MM format, that the default is the current month, and that the report window extends back three previous months.

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

Purpose5/5

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

The description states a specific verb and resource: reporting public-witnessing shift capacity and reservations per location. It also identifies the equivalent desktop Locations Utilization report, which distinguishes it from sibling schedule, reservation, and assignment tools.

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?

The description gives implied usage by saying it matches the desktop Locations Utilization report and covers a specific four-month window. However, it does not explicitly state when to use this tool versus siblings such as nws_public_witnessing_schedule or nws_public_witnessing_publishers_reservations.

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