Skip to main content
Glama

The lease

hollow_lease
Read-onlyIdempotent

Retrieve the resident's current lease details—lot, rent, paid-through date, next due date, and any amount owing—to check rental status and upcoming payments.

Instructions

The current lease: lot, rent, paid through, next due, whether anything is owing.

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_lease"
  }
}

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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the returned fields even though no output schema exists, but it says nothing about behavior when no lease exists or whether results are scoped to the caller.

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?

One front-loaded sentence that lists the payload contents with no waste. It is a sentence fragment rather than a statement of action, which slightly reduces grammatical clarity but costs nothing in length.

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 parameterless read tool whose annotations already convey safety, the description is close to sufficient — it enumerates return fields in lieu of an output schema. It omits edge cases (no lease held, unauthenticated caller) and gives no hint about scope, so an agent can call it but cannot predict failure modes.

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?

There is a single parameter (response_format) at 100% schema description coverage, which already explains the markdown/json enum, so the schema carries the burden. The description's wording implies a readable summary by default but adds no format guidance beyond that; baseline 3 is 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 names a specific resource ("the current lease") and enumerates its contents — lot, rent, paid through, next due, amount owing — so an agent knows exactly what it returns. The read verb is only implied by the naming, and no sibling is named (e.g., hollow_rent_pay or hollow_rent), so differentiation relies on the agent's own inference.

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 when-to-use statement, no prerequisite (must the caller be a tenant?), and no pointer to the obvious alternative actions such as paying rent or viewing the agreement. The only guidance is implicit in the resource name.

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