Skip to main content
Glama

Binyan.im · בניינים

Audit history

query_audit_history
Read-only

Read the change log for a building: who changed an apartment, a payment, or an expense.

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": "query_audit_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
buildingIdYes
entityTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds the useful scoping fact that results are confined to one building, but says nothing about ordering (newest first?), retention window, or the default/cap on returned entries.

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?

A single front-loaded sentence with the resource and scope stated before the enumeration of entity types. No filler or redundant restatement of the tool name.

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 three-parameter read tool with no output schema, the definition should describe the shape of an audit entry (actor, timestamp, entity, before/after) so the agent knows what it will receive. The description is adequate on scope but silent on return shape and on the limit semantics.

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 0%, so the description must carry parameter meaning; it does partially, implying buildingId is the building scope and that entityType covers apartment/payment/expense. The 'limit' parameter (default 50, max 1000) is never mentioned, leaving a third of the surface undocumented.

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 ('Read') and resource ('the change log for a building') and enumerates the entity types covered (apartment, payment, expense). It is clearly distinguishable from the list_*/create_*/update_* siblings, though it never names an alternative explicitly.

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 implied by the phrase 'change log ... who changed' — an agent can infer this is for auditing past modifications rather than fetching current state. There is no explicit when-to-use/when-not guidance and no pointer to a sibling for current-state queries.

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