Skip to main content
Glama
Sign In
Cyoda Calculation Node MCP

Cyoda Calculation Node MCP

Official
by Cyoda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

entity_get_entity_tool

Retrieve a single entity by its technical ID and entity model type, with an optional version.

Instructions

Retrieve a single entity by its technical ID.

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_model": "<entity_model>",
      "entity_id": "<entity_id>"
    },
    "name": "entity_get_entity_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_modelYesThe type of entity (e.g., 'laureate', 'subscriber', 'job')
entity_idYesThe technical UUID of the entity
entity_versionNoThe entity model version (default: from config)1

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the operation but does not disclose side effects, permissions, rate limits, or that it is a read-only operation. For a simple retrieval, this is minimally acceptable.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. Every word is necessary to convey the core purpose.

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?

Given the simple nature of the tool, the description is nearly complete. It does not explain error cases or return values, but the presence of an output schema helps fill those gaps. Still, it could mention that the entity is returned in full.

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?

Schema description coverage is 100%; each parameter (entity_model, entity_id, entity_version) already has a description in the schema. The tool description adds no additional meaning beyond what is already in the schema.

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 description 'Retrieve a single entity by its technical ID' clearly states the verb 'Retrieve', the resource 'a single entity', and the method 'by its technical ID'. This distinguishes it from sibling tools like entity_create_entity_tool, entity_delete_entity_tool, and entity_list_entities_tool.

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?

The description implies usage when the technical ID is known, but does not explicitly state when to use this tool versus alternatives like search tools for unknown IDs. No guidance on exclusions or alternatives is provided.

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

Deploy Server

Other Tools