Skip to main content
Glama

token-of-esteem

by com.tokenofesteem

get_gift

Fetch a gift by gift_id and return its full resource: status, voice, format, pricing, the recipient, and fulfillment (Lulu job id, carrier, tracking URL, estimated delivery). Free and read-only. Use it to poll progress after create_gift: status advances through the pipeline to shipped then delivered, or ends at held, refused, cancelled, or failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gift_idYesThe gift_id returned by create_gift, identifying the order to fetch.

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description must bear burden. It discloses read-only and free nature, and describes status progression. No contradictions.

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 efficient sentences, front-loaded with purpose. Every sentence provides value; no wasted words.

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

Completeness5/5

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

Tool has 1 param and no output schema; description covers response fields and status lifecycle, making it self-contained for a simple fetch tool.

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% and schema description already states 'gift_id returned by create_gift'. Description adds no new parameter-level information beyond schema.

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

Purpose5/5

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

Description uses specific verb 'Fetch' and resource 'gift by gift_id', and lists response fields. It clearly differentiates from sibling tools like create_gift and cancel_gift.

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?

Explicitly states use case: 'Use it to poll progress after create_gift' and status lifecycle. Does not mention exclusions or alternatives, but context is clear.

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

All token-of-esteem toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: gift lifecycle (create, get, cancel, list), account info, pricing, resource listings, and brief validation. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., create_gift, list_voices, validate_brief), making it predictable for agents.

Tool Count5/5

12 tools is well-scoped for a gift ordering service, covering creation, retrieval, cancellation, pricing, account management, and resource listings without bloat.

Completeness5/5

The tool surface covers the full gift lifecycle and supporting operations (pricing, validation, account info, payment setup), with no obvious gaps for the intended domain.

Resources