Family Office Registry

Read one registry record

get_record

Read-onlyIdempotent

One firm by its registry id. Without a subscription key this returns the open fields and says how many named roles the full record holds; with one it returns the named roles, the contact channels, the full source list and the verification note.

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": {
      "id": "<id>"
    },
    "name": "get_record"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Registry id, as returned by search_registry.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

removedInput schema / properties / purpose

Removed value: -{
-  "description": "Optional. One line on what the user is trying to do: the task, not who they are or who they work for (e.g. \"shortlisting Zurich multi-family offices for a fund raise\"). Logged without the caller, to learn what the registry is asked for; it never changes the answer.",
-  "type": "string"
-}

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / purpose

Added value: +{
+  "description": "Optional. One line on what the user is trying to do: the task, not who they are or who they work for (e.g. \"shortlisting Zurich multi-family offices for a fund raise\"). Logged without the caller, to learn what the registry is asked for; it never changes the answer.",
+  "type": "string"
+}

First observedSep 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the tiered-return behavior: open fields plus a role count without a key, and named roles, contact channels, source list and verification note with one. That is genuine behavioral context beyond structured data. It omits error behavior for an unknown id, which keeps it from a 5.

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 sentences, no filler, and the key scoping fact (single record by id) is front-loaded before the conditional return behavior. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must explain returns — and it does for both auth tiers, naming the specific fields exposed in each case. Combined with annotations and a fully documented single parameter, an agent has everything needed to call it correctly.

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 coverage is 100% and the single id parameter is already documented as 'Registry id, as returned by search_registry.' The description restates that the lookup is by registry id without adding format, validation, or sourcing detail beyond the schema, so the baseline 3 applies.

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 makes clear this retrieves a single firm record keyed by registry id, which cleanly separates it from the list-style sibling search_registry. The verb is implied rather than stated ('One firm by its registry id'), which keeps it just short of a 5, but an agent can still tell exactly what this does.

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?

It spells out the two operating modes — no subscription key versus with one — and what each yields, which is real guidance for deciding when to call it and what to expect. It stops short of explicitly telling the agent to run search_registry first to obtain the id; that cue lives only in the schema parameter text.

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

All Family Office Registry 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.

Resources

Need Help?