Skip to main content
Glama

Attify

Renewal packs

get_renewal_packs
Read-onlyIdempotent

The renewal packs your company signed for vendor negotiations: one agent and month each, the audited numbers it carries (claimed, audited, the audited share with its interval, cost per audited outcome), when it expires, and its signed attestation (check it with verify_attestation). Reading only: a new pack is signed in the app. Needs sign-in to Attify; reads only.

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_renewal_packs"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoOne agent's name or id.

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description still adds real context beyond them by stating the tool requires Attify sign-in and that pack creation happens elsewhere in the app. It also discloses that each record pairs one agent with one month and carries an attestation, which tells the agent how to interpret the rows. It stops short of describing pagination or result ordering.

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?

The payload contents are front-loaded in one dense clause, with the usage boundaries (read-only, sign-in, where to create packs) trailing in short fragments. Nothing is redundant, though the long parenthetical list makes the single sentence 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?

There is no output schema, so the description carries the burden of describing return values and does so field by field, including the expiry and attestation. Combined with the stated auth requirement and read-only constraint, an agent has enough to call it correctly and know what it will receive.

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%, with the single optional 'agent' parameter documented as a name or id, so the structural baseline applies. The description's phrase 'one agent and month each' clarifies the record grain but does not explicitly say the agent parameter filters results to that one agent, leaving the filtering semantics to the schema.

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 the resource (renewal packs the company signed) and enumerates the payload fields an agent will get back: agent/month, claimed vs audited numbers, audited share with interval, cost per audited outcome, expiry, and the signed attestation. That is far more specific than the title, though the verb is nominal rather than an explicit 'list/return', so it is clear what is returned but not how the call is framed.

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?

It routes one downstream step explicitly ('check it with verify_attestation') and states the read-only boundary ('a new pack is signed in the app'), which tells the agent this tool cannot create packs. It does not say when to prefer this over sibling data tools such as get_agent_outcomes or get_verdict, so selection between the pack view and the outcome views is left to inference.

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