Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

volumetrics_calculate

Calculates initial oil in place from reservoir properties and oil-water contact elevation, excluding recoverable reserves, and returns a job ID for tracking.

Instructions

Initial oil in place (not recoverable reserves) with fractional OWC; returns job_id.

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

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.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, closed-world behavior. The description adds that the call returns a job_id, which signals asynchronous job creation, but it does not explain permissions, job lifecycle, polling, or what happens after submission.

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

Conciseness5/5

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

The definition is a single, front-loaded sentence with no filler. Both clauses, the result scope and the returned job_id, carry useful information.

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

Completeness3/5

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

The rich schema and annotations cover most invocation details, and the description states that a job_id is returned. However, for a compute-job tool with no output schema, it should say more about the asynchronous workflow and what the agent should do with the returned job_id.

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 all parameters, including nested properties, contact_z_m, Bo, and execution settings, are already documented in the schema. The description adds only the 'fractional OWC' and 'not recoverable reserves' framing, without extra parameter syntax or constraints.

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 states a specific result: initial oil in place, explicitly not recoverable reserves, with fractional OWC. That distinguishes the calculation from reserve estimation, though it does not differentiate it from siblings such as regional_volumes or volumes_reconcile.

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 phrase 'not recoverable reserves' gives an implied scope boundary, but there is no explicit when-to-use guidance, no prerequisites, and no named alternative for reserve or reconciliation workflows. Usage is therefore only partially inferable.

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