DecisionPen MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_entity

Fetch a Confirmed map entity's description, aliases, and custom attributes by entity_id, optionally including relationships and related entity stubs.

Instructions

Fetch one Confirmed map entity (description, aliases, custom_attributes). Optionally include relationships / related entity stubs. entity_id: from search_entities.

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

Input Schema

Name	Required	Description	Default
`entity_id`	Yes
`include_relationships`	No
`include_related_entities`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden; 'Fetch' implies a read-only operation but this is never stated, nor are permissions, rate limits, or failure behavior for unknown ids. It does disclose that relationship and related-entity data is opt-in via flags, which is genuinely useful behavioral context beyond the schema titles.

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?

Front-loaded and only three short lines, with the returned-field summary in parentheses and the parameter note last. Slightly telegraphic phrasing costs it a point but nothing is wasted.

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-value explanation is not required, and the description covers the core fetch plus optional expansions. For a tool with zero annotations and 0% parameter coverage it could still say more about the 'Confirmed' status constraint and error behavior.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate: it identifies the entity_id source and explains that the two booleans pull relationships and related-entity stubs. Only slight gaps remain (no mention of the false defaults, no id format), so this adds real meaning over the bare titles.

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?

Specific verb plus resource: 'Fetch one Confirmed map entity' and it enumerates the returned fields (description, aliases, custom_attributes). The singular scope implicitly separates it from batch_get_entities and from get_entity_relationships, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

It does provide a routing hint for the required input ('entity_id: from search_entities'), which tells the agent where the identifier comes from. However, there is no guidance on when to choose this over get_entity_relationships or batch_get_entities, and no exclusions or preconditions.

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

Deploy Server