DecisionPen MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_entity_evidence

Retrieve linked evidence fragments and a summary for a resolved entity ID, returning fragment IDs and source titles to cite in map-grounded answers.

Instructions

Unstructured evidence pack for one entity: linked fragments + summary_node. Use after resolving CTMS/EDC/any app id. Cite fragment_id and source_title. Do not promote note-only integrations to Confirmed map edges.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_entity_evidence"
  }
}

Input Schema

Name	Required	Description	Default
`entity_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the returned structure (linked fragments plus summary_node) and one integrity caveat about Confirmed map edges, but it never states that the call is read-only, whether results are paginated or truncated, or what 'note-only' integrations actually are.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool returns before the usage and citation rules. The telegraphic phrasing ('linked fragments + summary_node', 'Confirmed map edges') is efficient but assumes domain vocabulary, costing some clarity.

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?

An output schema exists, so return values needn't be spelled out, and the tool is a simple one-parameter read. Still, with no annotations the description should say more about safe-read behavior and result size limits than the single integrity caveat it provides.

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?

Only one parameter, entity_id, at 0% schema description coverage. The description compensates partially by implying it must be an id already resolved from CTMS/EDC/any app, which is useful meaning beyond the bare schema, but it gives no format, example, or failure behavior for an unresolved id.

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: returns an 'Unstructured evidence pack for one entity' composed of 'linked fragments + summary_node'. That distinguishes it from get_entity or get_entity_relationships implicitly, though it never names a sibling to contrast with, so differentiation is left partly to inference.

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?

Gives a real sequencing precondition ('Use after resolving CTMS/EDC/any app id') rather than just describing the tool, plus an operational constraint about not promoting note-only integrations to Confirmed map edges. It stops short of naming an alternative such as search_evidence or get_document for cases where the entity id is not yet known.

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

Deploy Server