Skip to main content
Glama

AceRound AI Interview Copilot

get_gift_code_info

Read-only

Look up a gift code: what it includes, whether it has expired or run out, and whether this account can redeem it. (Requires the user's sign-in with scope account:read.)

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

Input Schema

NameRequiredDescriptionDefault
codeYesGift code

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=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context the annotations cannot express: the required sign-in scope account:read, plus a preview of the three facts returned. It does not discuss error behavior for invalid codes or rate limits.

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 sentence plus a parenthetical, with the purpose front-loaded and the authorization caveat demoted to the end where it belongs. No filler or redundant restatement of the title.

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?

With no output schema, the description compensates by summarizing the returned fields (contents, expiry, redeemability), and it covers the auth prerequisite. For a single-parameter read tool this is nearly complete; only invalid-code behavior is left unspecified, which is minor.

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% for the single "code" parameter with length bounds already documented, so the schema carries the weight. The description adds nothing about code format, case sensitivity, or normalization, which is acceptable at baseline 3.

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 ("Look up") and resource ("gift code") and enumerates what is returned: contents, expiry/exhaustion status, and per-account redeemability. This distinguishes it in practice from the mutating redeem_gift_code sibling, though it never names that alternative 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 read-only framing ("whether this account can redeem it") implies this is a pre-redemption check rather than the redemption itself, but there is no explicit when-to-use/when-not statement and no alternative tool is named. Usage is inferable, not prescribed.

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