Skip to main content
Glama

Changes on the pages Provkeep reads

list_changes
Read-onlyIdempotent

Lists the changes Provkeep found on the official pages it reads, newest first, for the products the signed-in account watches: which page, which state, when, what kind of change and which products it names, with the page's link. Optional state and number of days (default 30). 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_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days to look back. Default 30.
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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does: result ordering (newest first), account-scoped filtering, a default lookback window, and the quota-relevant note that it does not count as a lookup.

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?

It is a single dense sentence with the core purpose and scope front-loaded; every clause carries information about scope or returned fields. The run-on structure makes it slightly harder to scan than a two-sentence split would be.

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?

With only two optional parameters, full schema coverage, and no output schema, the description is nearly self-sufficient, and it usefully describes the returned fields. It does not mention result limits or pagination despite promising 'newest first', which is the one remaining 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%, so both parameters are already documented, including the 30-day default and the two-letter/full-name state format. The description merely restates 'Optional state and number of days (default 30)' without adding format or edge-case detail, so the baseline 3 applies.

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?

Names a specific verb and resource ('Lists the changes Provkeep found on the official pages it reads') and narrows scope to 'the products the signed-in account watches', so it is distinguishable from siblings like list_audits or list_sources. It even enumerates what each change entry contains (page, state, when, change kind, named products, link).

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 by the scoping ('products the signed-in account watches') and the note that it 'does not count as a lookup', which hints at a cost/quota distinction. However, there is no explicit when-to-use versus when-not guidance and no named alternative for broader or historical change queries.

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