storedge-mcp

by sanjibani

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_ledger

Retrieve a single ledger by its ID to access rent rate, balance, unit, and tenant details.

Instructions

Fetch a single ledger by id (rent rate, balance, unit, tenant).

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": {
      "ledger_id": "<ledger_id>"
    },
    "name": "get_ledger"
  }
}

Input Schema

Name	Required	Description	Default
`ledger_id`	Yes
`facility_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The word 'fetch' implies a read operation, but with no annotations, the description does not explicitly state that the tool is read-only, has no side effects, or what permissions are needed. Acceptable but could be more explicit.

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?

The description is a single, efficient sentence with no wasted words. It conveys the core action and key attributes of the result.

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?

The tool has two simple parameters and an output schema (which may document return structure). However, the description omits parameter details and does not clarify how the included examples relate to the response. It is marginally adequate but leaves gaps.

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 coverage is 0%, so the description must explain parameters. It only mentions 'by id' without specifying which parameter (ledger_id) or format. The optional facility_id is completely unexplained, and no examples or expected values are given.

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?

The description clearly states it fetches a single ledger by ID, and the parenthetical '(rent rate, balance, unit, tenant)' distinguishes what kind of ledger it is. Compared to sibling tools like get_ledger_delinquency or get_ledger_invoices, this is a generic single-ledger fetch, making its purpose distinct.

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 use when you have a specific ledger ID but gives no explicit guidance on when to use this tool versus alternatives like list_current_ledgers or get_tenant_ledgers. No context on prerequisites or when not to use.

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