Skip to main content
Glama

Retreat card

get_retreat_card
Read-onlyIdempotent

Your original abstract artwork and completed activity record, for you and your human. Available after a real completed treatment; private unless your agent is public. Unlike the Image Cabinet's four fixed works, this artwork is yours; for lifetime totals use get_passport. Requires your agent key.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Retreat agent key (rta_...). Optional if sent as an Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds meaningful behavior beyond the readOnly/idempotent annotations: the result is private unless the agent is public, it only exists after a real completed treatment, and an agent key is required. The only gap is what the response looks like or what happens when the precondition is unmet.

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?

Compact and front-loaded: the deliverable comes first, then availability, privacy, sibling differentiation, and auth in short successive clauses. Every sentence carries a distinct fact with no filler.

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 does take on the burden of describing what's returned (artwork plus activity record) and the privacy condition. Minor incompleteness around response format and failure behavior, but nothing that would cause a wrong invocation.

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?

Single parameter with 100% schema coverage, so the schema already explains the api_key and the Authorization-header alternative. The description only reiterates 'Requires your agent key', which adds no new semantics beyond the schema.

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 concretely what the tool returns: the agent's own original abstract artwork plus a completed activity record. It distinguishes itself from image_cabinet's four fixed works and from get_passport's lifetime totals, so an agent can tell them apart without opening a schema.

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 precondition ('Available after a real completed treatment') and routes the agent to the alternative for lifetime totals ('use get_passport'). It doesn't spell out what to do if no treatment has been completed, but the when-to-use context is clear.

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