Skip to main content
Glama
petropt

petropt/petro-mcp

havlena_odeh

Performs oil material balance analysis with the Havlena-Odeh method to identify reservoir drive mechanisms and estimate Original Oil In Place (OOIP) from production and PVT data.

Instructions

Oil material balance using Havlena-Odeh straight-line method (1963).

Identifies drive mechanism (depletion, gas cap, water drive) and estimates Original Oil In Place (OOIP). Returns F vs Et plot data for diagnostics.

Args: pressures: Reservoir pressures at each time step (psi). np_values: Cumulative oil production at each step (STB). rp_values: Cumulative producing GOR at each step (scf/STB). wp_values: Cumulative water production at each step (STB). wi_values: Cumulative water injection at each step (STB). bo_values: Oil FVF at each pressure (bbl/STB). rs_values: Solution GOR at each pressure (scf/STB). bg_values: Gas FVF at each pressure (bbl/scf). bw_values: Water FVF at each pressure (bbl/STB). boi: Initial oil FVF (bbl/STB). rsi: Initial solution GOR (scf/STB). bgi: Initial gas FVF (bbl/scf). cf: Formation compressibility (1/psi). Optional. swi: Initial water saturation (fraction, 0-1). Optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pressuresYes
np_valuesYes
rp_valuesYes
wp_valuesYes
wi_valuesYes
bo_valuesYes
rs_valuesYes
bg_valuesYes
bw_valuesYes
boiYes
rsiYes
bgiYes
cfNo
swiNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions returning plot data but does not state whether the tool is read-only, destructive, or has prerequisites. Side effects or required permissions are absent.

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?

The description is front-loaded with purpose and then lists parameters in a structured block. It is concise enough but could be slightly tighter by removing redundant units explanations.

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?

Given the tool's complexity (14 parameters, specialized domain) and absence of annotations, the description adequately covers purpose and parameter meanings. However, it lacks behavioral guidelines and algorithm details, relying on the output schema for return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 14 parameters are listed with units and brief context (e.g., 'psi', 'STB'), compensating for the 0% schema description coverage. However, it does not explain array length consistency or the relationship between parameters, leaving some ambiguity.

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?

The description clearly states it implements the Havlena-Odeh straight-line method for oil material balance, identifying drive mechanisms and estimating OOIP. It specifies the returned diagnostic plot, distinguishing it from other reservoir engineering tools like volumetric calculations.

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?

No guidance is provided on when to use this tool versus alternatives such as pz_analysis or rta_flowing_material_balance. The description implies it's for material balance analysis but lacks explicit conditions or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/petropt/petro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server