EstatePlan.now

Get one firm's record

get_firm

Read-onlyIdempotent

The full public record for one listed firm, by its slug (from search_firms or a profile URL /firms/).

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": {
      "slug": "<slug>"
    },
    "name": "get_firm"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Firm slug, e.g. "myatt-bell".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/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 the 'full public record' framing but does not disclose return shape, behavior for unknown slugs, or whether unlisted firms are inaccessible — gaps for a lookup tool.

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 sentence, front-loaded with the resource and scoping detail, with the parenthetical carrying only the provenance an agent needs. No redundant wording.

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 one-parameter read with 100% schema coverage and full annotations, it is close to complete. However, 'full public record' leaves the returned content vague and there is no output schema to compensate, so one clause on what comes back would close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already gives an example value. The description earns credit by explaining slug provenance (from search_firms or a /firms/<slug> URL), which the schema does not provide.

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?

Specific verb, resource, and scope: 'The full public record for one listed firm, by its slug'. It also distinguishes itself from search_firms by positioning that sibling as the source of slugs rather than an alternative lookup method.

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 tells the agent where the slug comes from (search_firms or a /firms/<slug> profile URL), which is the practical precondition for using this tool. It stops short of explicit when-not conditions or contrasting itself with the other siblings.

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

All EstatePlan.now 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?