Skip to main content
Glama

Read a sign

hollow_read_sign
Read-onlyIdempotent

Reads a town sign's text by its ID, letting you inspect or quote what the sign says.

Instructions

The text of a sign by its id (signs are listed by hollow_town).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sign": "<sign>"
    },
    "name": "hollow_read_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
signYesThe sign id
response_formatNo"markdown" for readable text (the default), "json" for the town's whole answer as structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that: no statement about what happens for an unknown or deleted id, no notion of visibility or permissions, and nothing about the open-world/live-state nature of the answer.

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?

One short sentence with the return value front-loaded and the parenthetical pointer to hollow_town placed where it is useful. Nothing is padded or repeated.

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

Completeness3/5

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

For a simple two-parameter read with a fully documented schema and rich annotations, most of what an agent needs is present, and the returned value (the sign's text) is stated. The gaps are edge-case behavior for missing ids and any hint that the content reflects live world state, neither of which is covered elsewhere since there is no output schema.

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%, with both 'sign' (the sign id) and 'response_format' (markdown vs json, with default) documented inline. The description only restates the id lookup and says nothing about the response_format choice, so it adds no meaning beyond the schema. Baseline 3 applies.

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 names the resource (a sign), the lookup key (id), and the value returned (its text), so an agent knows exactly what it gets back. It also points at hollow_town as the source of sign ids, which separates it from the listing tool. It stops short of a verb-first statement, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Mentioning that signs are listed by hollow_town gives real routing context: an agent that has not yet seen a sign id knows where to go first. However, there is no explicit when-to-use or when-not framing, and no acknowledgement of the obvious alternate path of reading signs via hollow_town or hollow_look.

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