Skip to main content
Glama

Voicedex

recent_changes

Read-onlyIdempotent

Latest catalog changes, newest first: price changes, shutdown announcements, deprecations, models added. kind: one of price_changed, price_published, shutdown_announced, model_deprecated, model_removed, now_ga, model_added, provider_added, provider_retired.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
providerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context — results are ordered newest first — and enumerates the discrete event kinds, but says nothing about pagination, how deep the history goes, or what a 'limit' actually caps.

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?

Two sentences, front-loaded with the outcome and ordering, followed by the kind vocabulary. The long enumeration earns its place because those values exist nowhere in the schema; the only minor cost is that the inline list is dense enough to be easy to misread.

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?

An output schema exists, so return shape need not be described, and annotations cover the read-only safety profile. What remains thin is filter behavior — how `provider` is matched and what `limit` bounds — which is a modest gap for a three-parameter feed tool but not a blocking one.

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 0% and the schema types `kind` as a bare string, so the description's nine-value enumeration (price_changed, now_ga, provider_retired, etc.) is real added meaning that the agent could not get otherwise. However, `limit` and `provider` receive no explanation at all — no format for provider, no statement of whether limit is a cap, page size, or offset substitute — so the compensation is only partial.

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 names a specific resource (catalog changes) and its ordering (newest first), and enumerates the concrete event types it surfaces (price changes, shutdowns, deprecations, additions). An agent can tell this is a changelog/feed tool rather than a search or lookup tool, though it never explicitly contrasts itself with siblings like search_models or compare_models.

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 only implied: the enumeration of change types hints that an agent should call this when it wants recent announcements or price movements rather than current model data. There is no statement of when not to use it, no mention of alternatives for point-in-time lookups, and no prerequisite context such as rate limits or freshness windows.

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.