Skip to main content
Glama

Loyal Spark Holder

Claim Gift Certificate

claim_gift_certificate

Claim an active gift certificate; binds it to your wallet (status active -> pending_mint).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "claim_gift_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesGift certificate code to claim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context, the state transition active -> pending_mint on the claimed certificate, which tells the agent the effect is durable and non-instant (minting follows). It does not say what happens if the code is already claimed or invalid.

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?

One compact sentence with the action first and the state transition in parentheses. Every clause carries information; nothing is padded.

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 one-parameter mutation with no output schema and full annotation coverage, the definition supplies the essential idea (claim + wallet binding + resulting status). Minor gaps are failure behavior and return value, but nothing an agent needs before invoking it is seriously missing.

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?

With a single required parameter and 100% schema description coverage, the schema already explains 'code'. The description adds no format, casing, or validation detail beyond that, so the 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?

States a specific verb (claim) and resource (gift certificate) plus the scope constraint 'active', and clarifies the effect as binding to your wallet. This separates it from lookup_gift_certificate and list_my_gift_certificates, which read rather than claim, though no sibling is named 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 word 'active' implies a precondition — only active certificates are claimable — but the description never says so explicitly, nor does it route the agent to lookup_gift_certificate first to verify status or to list_my_gift_certificates to find a code. Usage is only inferable.

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