orbit-sentinel-mcp

Overview Schema Source Related Servers Discussions Admin

get_entity_dossier

Read-only

Retrieve a cross-source entity dossier by UUID, combining regulatory filings, SEC financial signals, sanctions screening hits, and asset footprint counts with recent samples in one call.

Instructions

Get a cross-source dossier for an entity (by UUID): regulatory filings, SEC financial signals, sanctions/export-control screening hits, and asset footprint (satellites, ground stations, federal awards, surety bonds) — counts plus recent samples in one call. The most complete single view of an operator. Set include_family=true to roll the totals up across the entity's corporate family.

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_entity_dossier"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Entity UUID
`include_family`	No	Roll the dossier up across the entity's corporate family (same legal entity grouped by shared CIK/FRN or matching name). Default false.
`family_confidence`	No	Family grouping strictness when include_family=true: 'high' (default; exact name / shared identifier) or 'medium' (also groups normalized-name matches like 'AT&T INC.' with 'AT&T Corp.').
`include_subsidiaries`	No	Also roll up the entity's direct subsidiaries (from authoritative SEC Exhibit-21 / GCAT parent links). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Jul 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, so safety is covered. The description adds what is aggregated, that results are 'counts plus recent samples' rather than exhaustive records, and that family rollup is opt-in — useful context an agent would not get from the annotations. It does not explain cost/latency or why idempotency is false (samples shift over time).

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, front-loaded with the verb and resource, then contents, then the family-rollup instruction. The em-dash parenthetical is dense but every clause names distinct sourced data, so nothing is wasted.

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

Completeness4/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 carries the return-shape burden and does so adequately ('counts plus recent samples in one call'). For a 4-parameter read-only aggregation tool this is nearly sufficient; minor gaps are latency/cost expectations and the absence of an explicit 'not exhaustive, use search_* for full records' caveat.

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 100%, with id, include_family, family_confidence, and include_subsidiaries all documented including defaults and enum-like values. The description only restates include_family's effect ('roll the totals up across the entity's corporate family'), adding no meaning beyond the schema, so 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?

States a specific verb and resource ('Get a cross-source dossier for an entity (by UUID)') and enumerates the included data domains (filings, SEC financials, screening hits, asset footprint) with counts plus samples. The line 'The most complete single view of an operator' implicitly positions it against narrower siblings like get_entity_profile, though it never names one.

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 enumeration of what is aggregated and by the explicit instruction to set include_family=true for corporate-family rollups. However, there is no explicit when-not-to-use guidance or named alternative (e.g. use get_entity_profile for a lightweight profile, or search_* tools for targeted queries), leaving routing to inference.

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