Skip to main content
Glama

Loyal Spark Holder

List My Gift Certificates

list_my_gift_certificates
Read-onlyIdempotent

List gift certificates claimed by your wallet with optional status filter.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 50).
statusNoFilter by certificate lifecycle status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive read with no external/open-world effects, so the safety profile is covered. The description adds the wallet-scoping constraint, but says nothing about ordering, truncation behavior when results exceed limit, or any auth/wallet prerequisite. With annotations carrying the safety burden, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb first and the qualifier ("with optional status filter") trailing. No filler, no repetition of the title, nothing that could be cut without losing meaning.

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 two-parameter, zero-required, read-only list tool with complete schema documentation and full annotation coverage, the description supplies the essential ownership scope and filter mention. The one remaining gap is return-shape/pagination hints, which are not covered by an output schema; minor given the tool's simplicity.

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%: both limit (with default 50) and the five-value status enum are fully documented in the schema. The description only restates that the status filter is optional, adding no syntax, default, or semantic detail beyond the schema. Baseline 3 applies.

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 pairs a specific verb ("List") with a specific resource ("gift certificates") and adds an ownership scope ("claimed by your wallet"), which is more than a restatement of the name. It stops short of distinguishing itself from near-siblings such as list_my_vouchers or lookup_gift_certificate, so an agent still has to infer the boundary.

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 ownership scope plus the optional status filter, so an agent can reasonably infer "use this to enumerate my own certificates, optionally narrowed by lifecycle state." There is no explicit when-to-use or when-not-to-use statement, and no named alternative for lookups of a single certificate or for claiming one.

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