Skip to main content
Glama

Binyan.im · בניינים

List payments

list_payments
Read-only

List payments (גבייה) for a building. Optional from and to dates filter the due date, as YYYY-MM-DD.

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": {
      "buildingId": "<buildingId>"
    },
    "name": "list_payments"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover readOnlyHint=true and openWorldHint=false, so the safety profile is set. The description usefully clarifies that the date range filters the due date rather than a payment date, which the schema cannot convey, but it says nothing about result volume, pagination, or the limit parameter's effect.

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?

Two short sentences, front-loaded with the action and resource, then the filtering detail. No filler, though the parenthetical Hebrew gloss adds length without operational value for tool selection.

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 four-parameter list tool with no output schema and zero schema coverage, the description should cover limit and default ordering behavior. It handles the date semantics well but leaves the remaining two parameters and return shape unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden. It explains from/to as due-date bounds in YYYY-MM-DD format, but leaves limit and buildingId entirely unaddressed beyond the bare "for a building" phrase, and does not state whether the range is inclusive.

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?

States a specific verb and resource ("List payments") and adds the Hebrew term גבייה plus the scoping to a building. It is clearly distinguishable from siblings like record_payment or update_payment, though it doesn't explicitly name an alternative.

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?

Implies usage via "for a building" and the optional date filter, but never states when to prefer this over list_unmatched_transactions or other listing tools, nor any prerequisites such as permissions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources