Skip to main content
Glama
mcp-123bail
by lydstyl

generate_receipt

Generate a rent receipt PDF (quittance de loyer) for a specified lease and month, returned as base64 for immediate download or delivery to tenants.

Instructions

Generate the rent receipt PDF (quittance de loyer) for a lease and a month. Returns the PDF as base64.

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": {
      "leaseId": "<leaseId>",
      "month": "<month>"
    },
    "name": "generate_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesMonth YYYY-MM (e.g. 2026-10)
leaseIdYesLease ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the full burden, but it does disclose the one non-obvious behavior: the result is a base64-encoded PDF rather than structured data. It says nothing about permissions, whether the receipt is stored server-side, idempotency, or PDF size limits, which leaves meaningful gaps for a generation tool.

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?

Two short sentences with zero filler; the action and scope come first and the return format follows. Every clause earns its place.

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 two-parameter generator with no output schema, the description covers the action, inputs, and return encoding, which is enough to call it correctly. It falls short of complete only in not addressing failure cases or prerequisites for the lease/month pair.

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%, so both parameters (month with its YYYY-MM example, and leaseId) are already documented, making 3 the baseline. The phrase "for a lease and a month" merely restates the schema and adds no format or constraint detail beyond it.

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?

States a specific verb and resource ("Generate the rent receipt PDF (quittance de loyer)") plus its scoping inputs (a lease and a month). No sibling in the catalog produces receipts, so an agent can unambiguously pick this tool without opening the schema.

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?

Usage is only implied: the description names the inputs needed (lease and month), which suggests when the tool applies, but there is no explicit when-to-use, no preconditions (e.g. lease must exist/be active), and no mention of alternatives for retrieving payment history instead.

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