Skip to main content
Glama

Loyal Spark Holder

List My Vouchers

list_my_vouchers
Read-onlyIdempotent

List vouchers issued to your wallet (active, used, expired) across enrolled loyalty programs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/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 the safety profile is fully covered by structured data. The description adds that results span all three lifecycle states and all enrolled programs, which is useful behavioral context, but it says nothing about ordering, pagination, or what an empty wallet returns. With annotations doing the heavy lifting, a 3 is appropriate.

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 sentence with zero waste, front-loading the verb and resource before the scope qualifiers. Every clause (wallet, statuses, enrolled programs) adds discriminating information.

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 zero-argument, read-only list tool with rich annotations, the definition covers scope and coverage well enough to call it confidently. The only shortfall is that no output schema exists, so a hint about the voucher record shape or result ordering would have closed the last gap.

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?

Zero parameters, which is the baseline-4 case; the description correctly signals the tool takes no filters by stating the full status and program scope up front. Nothing in the text contradicts the empty 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?

Specific verb (list) plus resource (vouchers) with clear scope: vouchers issued to your wallet, across enrolled loyalty programs, covering active/used/expired statuses. It implicitly separates from list_my_gift_certificates and list_my_loyalty_balances by naming a different resource, though it never names a sibling explicitly.

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?

The status parenthetical and 'across enrolled loyalty programs' imply this is the unfiltered, all-program view, so an agent can infer it needs no scoping arguments. There is no explicit when-to-use vs. when-to-use-an-alternative statement, and no mention of prerequisites such as having enrolled programs.

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