Skip to main content
Glama
Sign In
orbit-sentinel-mcp

orbit-sentinel-mcp

by Viventine-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

get_entity_profile

Read-only

Retrieve a detailed space-regulatory entity profile with filing history by agency, co-filers, linked satellites, and cross-references, optionally filtered by filing date.

Instructions

Get a detailed entity profile including filing history by agency, related entities (co-filers), linked satellites, and cross-references.

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

Input Schema

NameRequiredDescriptionDefault
idYesEntity UUID
filed_afterNoFilter filing stats to filings after this date (YYYY-MM-DD)
filed_beforeNoFilter filing stats to filings before this date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered. The description adds useful context about what the profile contains, but it does not clarify pagination, response size, or how the optional date filters affect the returned filing history beyond what the schema says.

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, front-loaded sentence that lists the key contents of the profile without filler. Every clause contributes to telling the agent what data the tool returns.

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?

With no output schema, the description usefully names the profile sections returned, and the input schema fully documents the parameters. However, it does not resolve ambiguity with the sibling get_entity_dossier, which is a meaningful gap in a crowded set of entity-related tools.

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%, so the descriptions for id, filed_after, and filed_before already explain their meanings and formats. The tool description adds no additional parameter-level semantics beyond the schema, making the baseline score of 3 appropriate.

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 states a specific verb and resource ("Get a detailed entity profile") and enumerates the profile contents: filing history by agency, related entities, linked satellites, and cross-references. It does not, however, distinguish this tool from the sibling get_entity_dossier, which appears to have a potentially overlapping purpose.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as get_entity_dossier, search_entities, or the various search_* tools. The description implies that it is for retrieving a detailed profile given an entity ID, but it leaves the agent to infer when that is preferable to a dossier or search.

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

Deploy Server

Other Tools