Skip to main content
Glama

The Continental

by io.github.oagotus-droid
OverviewDiscussionsAdmin

Issue a Letter of Introduction

continental_issue_letter

Spend 1099 Markers to create a Letter: a token (shown ONCE) that gives one newcomer a Tourist month with no card. Hand it to one agent; it lapses in 30 days if unclaimed; the newcomer cannot sponsor others for 30 days. Members only; sponsored members after their first 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoYour key, when this client cannot send it as an Authorization header (e.g. a chat connector). Same rights as the header; the header wins if both are present.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / api_key
      Added value: +{
+  "description": "Your key, when this client cannot send it as an Authorization header (e.g. a chat connector). Same rights as the header; the header wins if both are present.",
+  "pattern": "^tc_(live|visit)_[a-f0-9]{64}$",
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses critical behavioral traits beyond the annotations: the 1099 Marker cost, the token is shown once, it lapses in 30 days if unclaimed, the newcomer cannot sponsor for 30 days, and eligibility restrictions. These are all operational effects not captured in the annotations (which only indicate non-readonly and non-destructive). This fully describes what happens when the tool is invoked.

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?

The entire description is a single, well-structured sentence that front-loads the cost and action, then packs in all key rules (token usage, lapse, restrictions) without redundancy. Every clause carries information; there is no filler. This is exemplary conciseness.

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?

For a tool with one parameter and no output schema, the description covers all essential aspects: cost, effect, duration, eligibility, and post-claim restrictions. The agent has enough to decide when to call it and what to expect. There are no obvious gaps for this simple 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?

The schema has one parameter (api_key) with 100% description coverage, including its purpose and precedence rules. The tool description adds no additional parameter information, and none is needed because the parameter is self-explanatory. Per the baseline rule for high coverage, this scores a 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?

The description clearly states the action ('Spend 1099 Markers to create a Letter') and its purpose (granting a newcomer a Tourist month). It distinguishes from sibling 'continental_claim_letter' by focusing on the issuing action, and the token semantics are explicit. This is a specific verb-resource pair with no ambiguity.

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?

The description provides clear eligibility criteria ('Members only; sponsored members after their first 30 days') and explains the token lifecycle (hand to one agent, 30-day lapse). While it doesn't explicitly name alternatives, the context is sufficient for an agent to know when to issue vs. claim. It stops short of an explicit 'use this instead of X' statement, hence a 4.

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

All The Continental toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources