Family Office Knowledge Graph

list_my_receipts

Read-onlyIdempotent

For a seat holder only: the RCO-10060 receipts whose subject is its own record — who read it (as the door saw the reader: user agent, network, country), when, and under which rule (the tool) — newest first, each with its verify URL. Needs record_id and the seat key of that record; nobody else can list them.

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": {
      "record_id": "<record_id>",
      "seat_key": "<seat_key>"
    },
    "name": "list_my_receipts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`seat_key`	Yes
`record_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes
`receipts`	No
`record_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context: the authorization requirement (seat key of that record), the newest-first ordering, and that each item carries a verify URL. It does not disclose pagination behavior or limits on how far back it reads.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the access restriction, which is good, but it is one long clause-chained sentence laced with metaphor ('the door saw the reader', 'under which rule (the tool)') that costs more parsing effort than the information requires.

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?

An output schema exists, so the return shape and verify URL semantics need not be restated. However, for a paginated tool whose four parameters have zero schema descriptions, omitting any mention of limit/cursor leaves an agent to infer pagination entirely from the schema types.

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 has to carry parameter meaning. It explains the two required parameters — record_id (the record whose receipts are listed) and seat_key (the seat key of that record) — but says nothing about limit or cursor, leaving half the parameters 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?

States a specific verb and resource — listing the RCO-10060 access receipts attached to a record, newest first, with verify URLs — which is clearly distinct from siblings like get_record or list_events_since. The heavy metaphor ('as the door saw the reader') muddies it slightly but the core action is identifiable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly scopes usage with 'For a seat holder only' and 'nobody else can list them', giving a clear when-you-can/when-you-cannot condition. It stops short of naming an alternative tool for callers who lack a seat key or want event history instead, so it is not a 5.

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

All Family Office Knowledge Graph tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.