Skip to main content
Glama
petropt

petropt/petro-mcp

calculate_simandoux_sw

Calculate water saturation in shaly sands with the Simandoux equation. Input true resistivity, porosity, water resistivity, shale volume, and shale resistivity to determine hydrocarbon presence.

Instructions

Calculate water saturation using Simandoux equation (shaly sands).

Args: rt: True formation resistivity (ohm-m). phi: Porosity (fraction v/v, 0-1). rw: Formation water resistivity (ohm-m). vshale: Shale volume (fraction v/v, 0-1). rsh: Shale resistivity (ohm-m). a: Tortuosity factor. Default 1.0. m: Cementation exponent. Default 2.0. n: Saturation exponent. Default 2.0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rtYes
phiYes
rwYes
vshaleYes
rshYes
aNo
mNo
nNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Minimal behavioral disclosure beyond being a calculation. No annotations, but the tool is inherently read-only; lacks constraints or side effects description.

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?

Concise, well-structured with a clear purpose sentence followed by an Args list. No redundant information.

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?

Covers all parameters adequately; output schema exists so return values need no explanation. Lacks equation details or assumptions, but sufficient for use.

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?

With 0% schema description coverage, the Args section in the description provides units, defaults, and brief explanations for all 8 parameters, significantly enhancing understanding beyond the schema.

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?

Clearly states the tool calculates water saturation using the Simandoux equation for shaly sands, distinguishing it from other saturation models like Archie or Indonesian.

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 explicit guidance on when to use Simandoux over alternatives (e.g., Archie for clean sands). The context 'shaly sands' is implied but not contrasted with sibling tools.

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