Retrieve the current snapshot of a relationship between two entities, including provenance. Use it to inspect versioned connections or resolve relationship queries.
Get the current snapshot of a specific relationship with provenance
| Name | Required | Description | Default |
|---|---|---|---|
| source_entity_id | Yes | Source entity ID | |
| target_entity_id | Yes | Target entity ID | |
| relationship_type | Yes | Type of relationship |
Changes observed during successful MCP inspections.
v0.22.2Input schema / properties / relationship_type / enumPrevious value: -[
- "PART_OF",
- "CORRECTS",
- "REFERS_TO",
- "SETTLES",
- "DUPLICATE_OF",
- "DEPENDS_ON",
- "SUPERSEDES",
- "EMBEDS"
-]New value: +[
+ "PART_OF",
+ "CORRECTS",
+ "REFERS_TO",
+ "SETTLES",
+ "DUPLICATE_OF",
+ "DEPENDS_ON",
+ "SUPERSEDES",
+ "EMBEDS",
+ "works_at",
+ "owns",
+ "manages",
+ "part_of",
+ "related_to",
+ "depends_on",
+ "references",
+ "transacted_with",
+ "member_of",
+ "reports_to",
+ "located_at",
+ "created_by",
+ "funded_by",
+ "acquired_by",
+ "subsidiary_of",
+ "partner_of",
+ "competitor_of",
+ "supplies_to",
+ "contracted_with",
+ "invested_in"
+]v0.15.0v0.14.0v0.12.1v0.11.0v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. 'Get' implies a read-only operation, but it does not state permissions, side effects, rate limits, or what provenance is returned. The mention of provenance is useful context but remains undefined.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. It states the action, target resource, and a key qualifier efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema and no annotations, so the description should help explain what is returned. It does not describe the snapshot contents, provenance structure, error behavior, or relationship direction, leaving significant gaps for an agent to call and interpret the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents all three required parameters, including the relationship_type enum. The description adds no additional meaning about parameter formats, directionality, or valid combinations beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Get') and resource ('current snapshot of a specific relationship') and adds the qualifier 'with provenance'. It is clear what the tool does, though it does not explicitly name or distinguish itself from sibling tools like retrieve_entity_snapshot or retrieve_field_provenance.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as retrieve_entity_snapshot, retrieve_field_provenance, or list_relationships. It also gives no prerequisites, exclusions, or context for selecting this snapshot-retrieval tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.