Skip to main content
Glama

How to make a gift link

how_to_gift
Read-only

Explain how, after buying a piece, to make a signed gift link with an optional plain-text note for a person (a birthday, a thank-you, the end of a project). Returns the exact endpoint to call with your access token. Free.

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

Input Schema

NameRequiredDescriptionDefault
idNoOptional catalogue id, entry number or title of the piece you bought.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses that the caller must supply an access token and execute the returned endpoint themselves, plus that the operation is free — genuinely useful behavioral context not present in the annotations.

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

Conciseness4/5

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

Purpose is front-loaded in a single well-formed sentence, with examples of note contexts in parentheses. The trailing one-word 'Free.' is slightly abrupt but carries real decision value, so the size and ordering are close to optimal.

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?

For a documentation-style tool with one optional parameter and no output schema, the description covers what is returned (the endpoint), the auth requirement, the cost, and the point in the workflow at which to call it. Only the omitted-id behavior is left unstated, a minor gap.

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 100% and the single optional 'id' is fully documented in the schema as catalogue id, entry number or title. The description only implies the id refers to a piece already purchased and never explains what happens when it is omitted, so it adds little beyond the schema — baseline 3.

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?

States a specific verb and resource ('Explain how ... to make a signed gift link') and, crucially, clarifies that the tool returns 'the exact endpoint to call' rather than performing the action itself. That distinction separates it from the action-oriented siblings like how_to_buy without needing to name them.

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?

Gives a clear precondition and sequencing cue: use it 'after buying a piece'. The trailing 'Free.' also signals there is no cost barrier. It stops short of stating when not to use it or naming an alternate route (e.g., the actual link-creation call), which keeps it below a 5.

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