Skip to main content
Glama

What Provkeep reads in a state

list_sources
Read-onlyIdempotent

Lists the official sources Provkeep reads every night in one state, or federally when no state is given, whether each answered on its latest reading and when. Shows how much a silence in that state tells you. Does not count as a lookup.

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": "list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoA US state, as its two letter code (OH) or its name (Ohio).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real behavior beyond them: sources are read nightly, the result reports whether each answered on its latest reading and when, and the call carries no lookup cost — freshness and quota context an agent cannot get from the annotations.

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?

Three short sentences, front-loaded with what is listed and the scope default, then the freshness and interpretation detail. Every sentence carries information, though 'Shows how much a silence in that state tells you' is phrased obliquely enough to require a second read.

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?

For a simple read-only, single-parameter list tool with no output schema, the description covers scope, default behavior, the shape of the answer (answered status plus timestamp) and cost semantics. What the individual source records look like is left implicit, which is the only notable gap.

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 coverage is 100% for the single optional state parameter, so the baseline is 3. The description does add the meaningful semantic that omitting state falls back to federal scope, which the schema does not state, but nothing further about accepted formats beyond what the schema documents.

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?

States a specific verb and resource: it lists the official sources Provkeep reads, scoped to one state or federally. That resource ('sources Provkeep reads nightly') is distinguishable from the list_* siblings covering audits, changes, lots, orders, products and watched products, though it never names a sibling explicitly.

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?

Usage is implied rather than stated: 'Shows how much a silence in that state tells you' suggests this is a coverage/confidence check, and 'Does not count as a lookup' implies a metered lookup tool exists elsewhere. There is no explicit when-to-use or when-not-to-use guidance naming an alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources