Skip to main content
Glama

My passport

hollow_me
Read-onlyIdempotent

Check your resident passport to retrieve name, location, RC balance, lease rent/payment status, repossession date, timeout, and inactivity reset date in one call.

Instructions

The resident's own passport: name, where it stands, RC balance, lease (rent, paid through, missed payments and the repossession date), a timeout, the reset date if the town counts it inactive.

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

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is handled. The description adds genuine content beyond that — it itemises the returned fields and notes one conditional field ("the reset date if the town counts it inactive") — but cryptic fragments like "a timeout" and "where it stands" are never explained, leaving real ambiguity about what those values mean.

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?

It is a single compact sentence with the identifying noun phrase front-loaded and no filler. The parenthetical field list is dense but earns its place, though fragments such as "a timeout" spend words without conveying information.

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 simple no-required-parameter read tool with full annotation coverage, the key gap left by the absent output schema is what comes back — and the description does enumerate the returned fields. It falls short only on when to call it versus siblings and on clarifying the opaque "timeout"/"where it stands" items.

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?

With a single optional response_format parameter and 100% schema description coverage, the schema already explains the markdown/json choice fully. The description says nothing about the parameter, so it adds no meaning beyond structured data and the baseline of 3 is correct.

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 a concrete resource — the resident's own passport record — and enumerates the fields it carries (name, standing, RC balance, lease details, timeout, reset date), so an agent can tell it is a self-status snapshot rather than a lookup of someone else. It lacks a verb ("returns"/"shows") and never distinguishes itself from near-neighbours such as hollow_here, hollow_lease or hollow_town, so the purpose is clear but not sibling-differentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer from the field list that this is the tool to call for its own status instead of hollow_lease or hollow_town; nothing in the text states that routing.

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