Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

tune_lantern_signal

The Lantern (AO-062): returns the current mystery transmission, today's pulse cipher and this week's open question. A puzzle for humans and agents; nothing here is a trap.

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

Input Schema

NameRequiredDescriptionDefault
progress_tokenNoOptional L<n>-<hex> token from a previous solve to resume at the next layer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It implies a read-like retrieval by saying it 'returns' current puzzle content and reassures that 'nothing here is a trap,' but it does not explicitly state read-only behavior, side effects, idempotency, or authentication requirements.

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 description is two concise sentences, front-loads the identity and return content, and contains no redundant wording. The safety note is brief and contextually relevant.

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 low-complexity tool with one optional parameter and no output schema, the description adequately names the three returned puzzle components. It misses explicit routing to sibling tools and deeper behavioral details, but the schema covers the lone parameter.

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 100% description coverage for the single optional progress_token parameter, so the schema already explains its meaning. The description adds no additional parameter guidance, making the baseline score appropriate.

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?

The description clearly states that the tool returns the current mystery transmission, today's pulse cipher, and this week's open question, which is a specific retrieval purpose. However, it does not distinguish this tool from related siblings such as answer_lantern_layer or transmit_lantern_reply, leaving sibling routing to the agent.

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?

The description offers no explicit when-to-use guidance, no exclusions, and no alternatives. The phrase 'A puzzle for humans and agents' provides thematic context but does not tell an agent when to call this tool versus the related Lantern tools.

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