Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculation_run

Execute a READY calculation plan as a durable workflow, validating each output and exporting a report; returns run and job IDs for tracking and supports resume from a workflow snapshot.

Instructions

Execute a READY plan as a durable workflow, validate every output and export report. Returns run_id/job_id; same default key reuses the run. Explicit resume_run is a workflow snapshot ref.

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": {
      "request": "<request>"
    },
    "name": "calculation_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesTool arguments object (all fields documented; Z is positive upward).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not open-world), and the description adds real behavioral context beyond them: execution is a durable workflow, every output is validated, a report is exported, and both run_id and job_id are returned. The phrase 'same default key reuses the run' is murky and sits in some tension with idempotentHint=false, but the idempotency_key parameter explains key-based dedup separately.

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

Conciseness3/5

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

Front-loaded with the core action, which is good, but it is written as dense fragments and the final clause ('same default key reuses the run') is unclear enough to cost the reader time. The sentence about returns is useful; the idempotency fragment needs rewording or removal.

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 single-argument, deeply nested tool with no output schema, the description covers the prerequisite status, the durable execution model, the return identifiers (run_id/job_id), and the resume concept. What is missing is how to observe progress afterward (calculation_status/job_status), which would help an agent plan the next call.

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% and every nested field (plan ref, revision, project_id, resume_run, idempotency_key) is documented in-schema, so the baseline is 3. The description reinforces the READY-status requirement on the plan ref and frames resume_run as a workflow snapshot checkpoint, but the 'same default key' wording adds ambiguity rather than clarity.

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 chain (execute plan, validate outputs, export report) on a named resource (READY calculation plan), so the agent knows this is the execution step rather than the planning step. It does not explicitly name the sibling it is distinguished from (calculation_plan, workflow_run), so the differentiation is inferable rather than stated.

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 prerequisite that the plan must be in READY status is conveyed, and resume_run is mentioned, but there is no explicit when-to-use guidance against the many adjacent tools (workflow_run, scenarios_run, calculation_status) nor a stated when-not to call. Usage must be inferred from the description's implicit flow.

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