DecisionPen MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

search_evidence

Run semantic search over DecisionPen evidence fragments to retrieve cited supporting passages; pass entity_id to scope results to one application or capability.

Instructions

Semantic search over DecisionPen evidence fragments (no generative answer). Prefer passing entity_id to scope to one application/capability. Prefer get_entity_evidence for the full linked pack of one entity. query: search text. limit: max fragments (1–50). entity_id: strongly recommended — filter to fragments linked to that entity.

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": {
      "query": "<query>"
    },
    "name": "search_evidence"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`entity_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.4/5.0

Behavior3/5

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

The description usefully discloses that results are evidence fragments rather than a generated answer and that entity scoping covers fragments linked to that entity. Because no annotations are supplied, however, it carries the full disclosure burden and does not explicitly confirm read-only behavior or explain ranking, pagination, or other operational behavior.

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?

The definition is compact and front-loads the tool's purpose and non-generative behavior before usage guidance and parameter details. Recommending entity_id twice is mildly repetitive, although the two statements add different information about application scope and fragment linkage.

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?

For a simple three-parameter search tool with an output schema, the description covers the central operation, an important alternative, and every input. Minor invocation gaps remain, such as whether an omitted or empty entity_id performs an unscoped search and what kinds of queries work best.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by documenting all three parameters: query is search text, limit caps fragments at 1–50, and entity_id filters to linked fragments. It also supplies usage semantics absent from the schema, especially the strong recommendation to provide entity_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line gives a specific operation and resource: "Semantic search over DecisionPen evidence fragments," and clarifies that it does not produce a generative answer. The reference to get_entity_evidence further distinguishes fragment search from retrieving an entity's full linked evidence pack.

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

Usage Guidelines5/5

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

It explicitly recommends passing entity_id when searching within one application or capability. It also names the alternative to use when the agent wants "the full linked pack of one entity," providing a concrete condition for choosing get_entity_evidence instead.

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

Deploy Server