Skip to main content
Glama

gifts_buy_gift

Destructive

Purchase a gift through the Aeza API by specifying the amount and payment method, with optional styling, emojis, hue, and comment.

Instructions

Gifts buy gift POST /gifts

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": {
      "body": "<body>"
    },
    "name": "gifts_buy_gift"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered structurally. The description adds nothing on top: it does not say that a purchase spends real money, whether the amount is debited from a balance, whether the action is reversible, or which payment method is required.

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

Conciseness2/5

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

It is short, but that brevity comes from under-specification rather than efficiency. The only content is a duplicated name fragment and a raw endpoint path, which is noise for a tool-calling agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent purchase operation with a nested required body and no output schema, the description should explain cost implications, required fields, and the result of the call. It does none of that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for a nested body object with six sub-properties (amount, method, hue, style, emojis, comment), only two of which are required. The description supplies no meaning for any of them, so an agent must guess at units, allowed method values, and what hue/style/emojis control.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially a restatement of the tool name plus the HTTP route: "Gifts buy gift POST /gifts". It conveys no resource detail beyond the name (what a gift is here, what buying entails) and gives no basis to distinguish it from siblings such as gifts_edit or gifts_use_code.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text when purchasing a gift is the right call versus other gifts_* tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools