Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ensemble_plan

Read-onlyIdempotent

Plan and queue multi-case reservoir simulations by combining property realizations with schedules, setting execution policy, and validating expected case counts for a project.

Instructions

ensemble_plan

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

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

D1.4/5.0
Behavior1/5

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

The description discloses nothing about behavior. Annotations declare readOnlyHint=true and destructiveHint=true-equivalent false, yet the schema's idempotency_key language ("the same key returns the existing job instead of a duplicate") and required expected_case_count imply a planning/job-creating operation, so the agent gets conflicting implicit signals with no text to resolve them. No contradiction can be attributed to the description itself since it says nothing, but it fails to carry the burden.

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

Conciseness2/5

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

A single identifier is technically terse but is under-specification rather than conciseness; there is no front-loaded statement of action or intent. Nothing about the two-word content earns its place as a tool description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a highly complex tool: nested objects, arrays bounded 1–10 for both realizations and schedules, cross-field constraints (expected_case_count = realizations x schedules), and resume semantics. With no output schema and no annotations explaining the planning-vs-execution boundary, the near-empty description leaves the agent unable to call this correctly.

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 description adds zero meaning beyond the single top-level `request` parameter, but schema description coverage is 100% and the nested definitions (execution policy, property_realizations, schedules, expected_case_count) are thoroughly documented in-schema. Per the high-coverage baseline, a 3 is appropriate even with no parameter prose in the description.

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

Purpose1/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

There is no guidance whatsoever about when to call this tool versus ensemble_run, calculation_plan, simulation_case_create, or plan_validate. The agent is left to infer the entire workflow position from the schema alone.

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