Skip to main content
Glama
Sign In
Cyoda Calculation Node MCP

Cyoda Calculation Node MCP

Official
by Cyoda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

entity_list_entities_tool

Retrieve a list of all entities of a given type, with optional version filtering.

Instructions

List all entities of a specific type.

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>"
    },
    "name": "entity_list_entities_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_modelYesThe type of entity to list
entity_versionNoThe entity model version1

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral aspects such as pagination, sorting, limits, or error handling when the entity type is invalid. The agent has no insight into the tool's side effects or output characteristics.

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 description is a single, short sentence that is front-loaded with the core action. It is appropriately concise for a straightforward list operation.

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 low complexity (2 parameters, simple list operation) and the presence of an output schema, the description adequately conveys the tool's purpose. It lacks details on return format but the output schema may compensate.

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?

The input schema covers 100% of parameters with descriptions, so the description does not need to add much. However, it adds no extra context about the format of entity_model or version beyond what the schema provides.

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?

The description clearly states the tool lists all entities of a specific type, which distinguishes it from sibling tools that get, create, or update a single entity. However, it could be more precise about what constitutes 'entity type'.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives like search_find_all or entity_get_entity_tool. There is no mention of prerequisites or scenarios where this tool is inappropriate.

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