Skip to main content
Glama

RenewRoster

Monthly renewal report

get_report
Read-onlyIdempotent

Renewals due in a month (YYYY-MM, default current) with who pays and totals.

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

Input Schema

NameRequiredDescriptionDefault
periodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds the default-period behavior and hints at the response shape (per-payer breakdown plus totals), but says nothing about aggregation level, ordering, or what happens for a month with no renewals.

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?

One tight sentence with the key facts front-loaded: what is reported, the period format, the default, and what comes back. It is slightly telegraphic as a fragment, but there is no filler to cut.

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?

For a single optional parameter tool with full annotations and no output schema, the description covers the essentials. Gaps remain around result structure (is 'who pays' a per-client row set or a summary?), empty-result behavior, and how this report relates to the similar list_expiring/reminders tools.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the schema only gives a regex pattern with no text — so the description carries the burden, and it does: it names the parameter's format (YYYY-MM) and its default (current month). It stops short of stating timezone/month-boundary behavior or whether the period is inclusive.

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 resource and scope: renewals due in a given month, plus the payload it returns (who pays, totals). It is distinguishable from list-style siblings, though the description never names a competing tool or clarifies how it differs from list_expiring or get_reminders.

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?

No when-to-use or when-not-to-use guidance. With close siblings like list_expiring and get_reminders in the same namespace, an agent gets no signal about when this report is the right call versus those alternatives.

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.