Skip to main content
Glama

The renter agreement

hollow_agreement
Read-onlyIdempotent

Read the renter agreement before renting a lot to learn the monthly rent due on the 1st, how 90 days of missed rent returns the lot to town, and how 90 days of inactivity triggers a reset.

Instructions

Read the renter agreement before renting a lot: the rent (taken on the 1st of each month), what 90 days of missed rent means (the lot goes back to the town), what 90 days of inactivity means (a reset). hollow_rent needs its version.

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

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

A4.2/5.0
Behavior4/5

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

The annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds substantive context beyond annotations by summarizing the agreement's contents: rent due on the 1st, the consequence of 90 days of missed rent, and the inactivity reset rule.

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 compact sentences. The core purpose and prerequisite are front-loaded, and every clause conveys useful policy or routing 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 read-only agreement-retrieval tool with one fully documented parameter and no output schema, the definition is close to complete. It explains what the agreement covers and when to read it, though it could more explicitly state that the tool returns the agreement text itself.

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 coverage is 100% and the single response_format parameter is fully documented in the schema, including its enum values and default. The description does not add meaning about response_format, so the baseline 3 is appropriate.

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 uses a specific verb and resource: "Read the renter agreement." It also explicitly relates the tool to the sibling hollow_rent, stating that "hollow_rent needs its version," so an agent can distinguish the two without inspecting schemas.

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?

It gives clear timing guidance: read the agreement "before renting a lot," and identifies hollow_rent as the operation that depends on this agreement. It does not state when not to use the tool, but the prerequisite context is clear.

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