Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

eclipse_import

Imports static ECLIPSE DATA/GRDECL from a source folder, resolves revision-checked INCLUDE files, builds block geometry, preserves properties, and applies EQUALS/MULTIPLY/COPY/ADD/BOX operations.

Instructions

Import static ECLIPSE DATA/GRDECL from an owner folder, recursively resolving revision-checked relative INCLUDE inside it. Streams COORD/ZCORN to block geometry and preserves ACTNUM/PORO/NTG/PERMX/SWAT/FIPNUM/SATNUM/EQLNUM; applies explicit EQUALS/MULTIPLY/COPY/ADD/BOX/ENDBOX. Returns job_id then properties with import_report.json listing every unsupported keyword and NOT RUN scientific checks. CRS/datum/units and any missing-property defaults require explicit user input. Does not perform equilibrium or MINPV/pinch/simulator initialization.

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

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

A4.3/5.0
Behavior5/5

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

Annotations are minimal (all hints false/readOnly false) so the description carries the load, and it delivers: it discloses async job semantics ('Returns job_id then properties'), enumerates exactly which properties are preserved and which keywords are applied, and warns that import_report.json lists unsupported keywords and NOT RUN scientific checks. It also states the explicit-user-input requirement rather than allowing inference, which is exactly the kind of behavioral fact an agent needs before calling a data-creating import.

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?

Front-loaded with the core action and format, and every sentence adds scope, preserved data, or a limitation. It is a dense single paragraph with no structural breaks, which makes it slightly harder to scan than a bulleted form, but there is little waste.

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 complex, mutation-capable import with a deeply nested schema and no output schema, the description covers return shape (job_id + properties + import_report.json), limitations, and mandatory user-confirmed inputs. It omits the workflow prerequisites (source registration via source_list, revision pinning via source_scan) that live only in the schema, so it is strong but not fully self-contained.

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%, so the baseline is 3; the description adds framing that CRS/datum/units and missing-property defaults must be user-confirmed (reinforcing the crs, vertical_datum, length_unit and defaults fields) but does not explain block_cells, execution policy, or the EQUALS/MULTIPLY/COPY/ADD/BOX/ENDBOX handling as parameters. It restates values the schema already documents rather than extending them.

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?

States a specific verb and resource ('Import static ECLIPSE DATA/GRDECL') and immediately scopes it by format ('recursively resolving revision-checked relative INCLUDE'), which distinguishes it from the generic grid_import/geodata_import siblings even without naming them. The agent can tell what class of file this handles from the first clause.

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

Usage Guidelines4/5

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

Clear about boundaries in the negative: it 'Does not perform equilibrium or MINPV/pinch/simulator initialization,' and it requires explicit user input for CRS/datum/units and missing-property defaults. However, it never routes the agent to an alternative tool (e.g. plain grid_import or dataset_import) for the cases it excludes, so usage is clear but not fully disambiguated across the large sibling set.

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