Skip to main content
Glama

list_gift_card_entries

Read-onlyIdempotent

List balance changes for an issued gift card in the approved business. Use the card ID from list_gift_cards.

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": {
      "id": "<id>"
    },
    "name": "list_gift_card_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 a closed-world scope, so the safety profile is fully covered elsewhere. The description adds the useful framing that these are balance changes (transaction history, not the card object) within the approved business, but says nothing about ordering, entry volume, or how offset works. Given the annotation coverage, 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?

Two short sentences, zero filler, with the object of the operation front-loaded and the input-sourcing tip second. Nothing needs trimming.

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?

For a simple read-only listing tool with no output schema, the description covers what the tool returns conceptually but omits the paging behavior implied by the `offset` parameter and any sense of result ordering or magnitude. Adequate to invoke, incomplete for interpreting or iterating results.

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 description coverage is 0%, so the description must carry the load: it does explain that `id` is the card ID obtained from list_gift_cards, which is meaningful. However, `offset` is never acknowledged — no hint that results are paged or that the parameter controls a result window — leaving half the parameters unexplained in both schema and prose.

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 states a specific verb and resource — listing balance-change entries for one issued gift card — which is clearly distinct from the sibling list_gift_cards that enumerates the cards themselves. It stops short of an explicit contrast statement, but an agent can still separate the two tools from the wording alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use the card ID from list_gift_cards" establishes the prerequisite workflow and the origin of the required input, which is real selection guidance. It gives no when-not conditions and doesn't mention pagination-driven repeated calls, so it doesn't reach the top of the scale.

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