Skip to main content
Glama

Collect a gift code's pack

gift_code_pack

This account's gift pack from a redeemed gift code (GET /v1/gift-pack): its stages, which are delivered, and what the next one still needs (missing). Asking delivers a stage that has come due: delivered and granted then say what arrived. redeemed is false for an account that has redeemed no gift code.

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

Input Schema

NameRequiredDescriptionDefault
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties
      Added value: +{
      +  "token": {
      +    "description": "the token your login returned; pass it when a call answered not_logged_in after you logged in",
      +    "type": "string"
      +  }
      +}
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The most valuable disclosure is that a plain read call has a side effect ('asking delivers a stage that has come due'), which explains the non-readOnly, non-idempotent annotations and warns the agent not to poll carelessly. Beyond that it adds little: no statement about error conditions (e.g. not_logged_in handling beyond the token param), repeat-call behavior, or what consuming a stage costs.

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

Conciseness3/5

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

Front-loaded with the resource and endpoint, which is good, but the second half is a run-on that mixes three separate ideas (delivery side effect, field semantics, redeemed=false) using bare quoted field names whose status as output fields is not clearly introduced.

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?

An output schema exists, so return-value explanation is optional and the description's field notes are a bonus rather than a necessity. What is missing is the operational picture: whether repeated calls are safe, what happens when no stage is due, and how this differs from the sibling gift_pack.

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?

The single `token` parameter is fully documented in the schema (100% coverage), including the exact recovery condition (pass it when a call answered not_logged_in), and the description adds nothing about it. Baseline 3 applies since the schema does all the work.

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 precisely (this account's gift pack from a redeemed gift code) and pins it to the endpoint GET /v1/gift-pack, plus enumerates the content: stages, what is delivered, and the next stage's `missing` requirement. The 'gift code' qualifier implicitly separates it from the sibling gift_pack, though that contrast is never made explicit.

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 gives one strong usage fact: calling the tool itself delivers a stage that has come due, and `redeemed: false` signals an account that never redeemed a code. There is no explicit routing advice against siblings such as gift_pack or shop_packs, so selection still has to be inferred from the name.

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