Skip to main content
Glama

Binyan.im · בניינים

List expenses

list_expenses
Read-only

List expenses (הוצאות) for a building. Optional from and to dates filter the expense 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_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds useful context: it clarifies that from/to filter on the expense date and gives the expected YYYY-MM-DD format. It says nothing about result ordering, pagination, or truncation behavior, which matters for a list tool with a 500-item cap, so it only partially covers behavior beyond the annotations.

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, front-loaded with the resource and scope, followed by the filtering detail. Nothing is redundant and nothing needs to be re-read.

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 simple read-only list tool whose annotations cover the safety profile and which has no output schema to explain, the description covers the core purpose and the date filters. It is incomplete on limit and pagination semantics and on what the returned records contain, which an agent needs in order to call this correctly.

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 has to carry the burden of explaining parameters. It explains only the from/to filters, including their format, and leaves buildingId and limit without any explanation. The limit parameter in particular is left ambiguous: the description never says what limit controls, what happens when it is exceeded, or whether results are truncated or paged.

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 states a specific verb and resource: 'List expenses (הוצאות) for a building'. This is unambiguous and separable from siblings such as list_payments or list_apartments by the resource named. It stops short of explicit sibling differentiation, but the scope is still clear.

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?

The description implies usage by saying the tool lists expenses for a building and that date filters are optional, which suggests when the date params matter. It never states when to prefer this over alternatives, when not to use it, or any prerequisites such as the building existing or the caller needing access.

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