Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

simulation_submit

Submit a project simulation case to run with OPM Flow and receive a job result, or a clear error when the solver is unavailable.

Instructions

Run real OPM Flow; returns a job error when the solver is absent.

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

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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is covered. The description adds one real behavioral fact beyond that: the tool performs genuine OPM Flow execution and reports solver absence as a job error, implying asynchronous job semantics rather than a synchronous result. It omits other important traits such as whether a job id is returned or that job_status should be polled.

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?

A single front-loaded sentence with zero filler; the core action ('Run real OPM Flow') comes first. It is efficient, though the extreme brevity leaves it under-specified rather than tightly scoped.

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

Completeness2/5

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

This is a complex submission tool with a deeply nested schema (case artifact, execution policy, idempotency) and no output schema, yet the description is one sentence. It says nothing about what is returned (job handle), how to poll progress, or how it relates to simulation_deck_run, simulation_case_create and job_status.

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 the nested request object documents every field, including execution policy defaults, idempotency behavior, and placement constraints. The description adds no parameter-level meaning whatsoever, so the baseline 3 applies.

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 and resource: run real OPM Flow simulation. An agent can tell this is a submission/execution tool, but it does not distinguish itself from close siblings like simulation_deck_run or simulation_case_create, which an agent would also consider for running a case.

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?

There is no when-to-use guidance, no prerequisites (e.g. that a case artifact must first exist), and no named alternatives. The only contextual hint is that the solver may be absent, which is a failure mode rather than usage guidance.

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