Skip to main content
Glama

gifts_get_owned_gifts

Read-onlyIdempotent

Retrieves the gifts owned by the authenticated Aeza account, enabling an agent to list them through the API.

Instructions

Gifts get owned gifts GET /gifts

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered externally. The description contributes nothing behavioral on top of that — no return set size, pagination, ordering, or whether unclaimed/unused gifts are included.

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?

It is short, but the brevity comes from under-specification rather than economy: the first clause duplicates the tool name and the second is a bare endpoint path. It is front-loaded only in the trivial sense that there is almost nothing to front-load.

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 zero-parameter read tool with rich annotations, the essentials for calling it are covered externally, and no output schema exists so return documentation is not strictly required. Still, with no parameter schema to lean on, the description should say what collection is returned and whether it is paginated or scoped to the authenticated user.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the description cannot be faulted here. Baseline 4 applies.

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?

"Gifts get owned gifts" is a near-verbatim restatement of the tool name gifts_get_owned_gifts, with no verb clarity beyond the implied "get". The only added information is the raw endpoint "GET /gifts", which does not tell an agent what the returned collection actually contains (purchased gifts, gift inventory, sent gifts?).

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of the nearby alternatives such as gifts_get_by_code or gifts_get_gift_styles. The agent must infer from the name alone that this lists all owned gifts rather than fetching one by code, and nothing states prerequisites or whether the caller must be authenticated.

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