Skip to main content
Glama
mcp-123bail
by lydstyl

add_payment

Record a rent payment against a lease by specifying lease ID, amount in EUR, and payment date, so rental income stays accurately tracked.

Instructions

Record a rent payment for a lease

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": {
      "lease_id": "<lease_id>",
      "amount": "<amount>",
      "payment_date": "<payment_date>"
    },
    "name": "add_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional notes
amountYesAmount in EUR (decimal)
lease_idYesLease ID
payment_dateYesPayment date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a write operation. It does not say whether duplicate payments for the same lease and date are rejected, whether the call requires permissions, whether it affects payment summaries or receipts, or what error behavior looks like.

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?

A single front-loaded sentence with no filler, so nothing needs trimming. The terseness is a completeness problem rather than a conciseness one.

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

Completeness2/5

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

For a mutation tool with zero annotations, no output schema, and three required parameters, the description is too thin. An agent needs to know side effects (payment summaries, receipts) and any idempotency or validation rules before calling it, and none of that is present.

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 amount (EUR decimal), payment_date (YYYY-MM-DD), lease_id, and notes all documented inline, so the baseline is 3. The description adds no meaning beyond the schema, such as whether notes are surfaced on receipts or whether amounts may be partial payments.

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 gives a specific verb and resource ('Record a rent payment') tied to a parent entity ('for a lease'), which is enough to tell it apart from read-side siblings like get_payment_summary_by_landlord or generate_receipt. It stops short of naming the alternative to use when the goal is a receipt or a summary, so it is clear but not fully 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 when-to-use guidance, no mention of preconditions such as the lease already existing, and no pointer to siblings like generate_receipt for the follow-up step. The agent must infer context entirely from the name and schema.

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