Retrieve the current snapshot of a specific relationship between two entities, including provenance, to verify its exact state.
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.15.0v0.14.0v0.12.1v0.11.0v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It mentions 'snapshot' and 'provenance' but does not clarify read-only nature, permission requirements, or side effects. Minimal behavioral disclosure.
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?
Single sentence, front-loaded with verb and object, no redundant words. Efficient and to the point.
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?
Despite having 3 required parameters and an enum, the description does not explain the shape of the snapshot or how provenance is represented. Without an output schema, more detail is needed for an agent to understand what to expect.
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% with clear parameter descriptions. The tool description adds only 'with provenance' which is not parameter-specific. Baseline of 3 is appropriate as schema already documents parameters well.
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 clearly states the action (get), object (snapshot of a specific relationship), and includes relevant detail (with provenance). It distinguishes from sibling tools like list_relationships and retrieve_entity_snapshot.
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?
No guidance on when to use this tool vs alternatives like list_relationships or retrieve_entity_snapshot. The description does not mention any prerequisites or conditions for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.