Skip to main content
Glama
petropt

petropt/petro-mcp

calculate_bit_pressure_drop

Calculate pressure drop across the drill bit using mud weight, flow rate, and total flow area.

Instructions

Calculate pressure drop across the bit (dP = MW * Q^2 / (12032 * TFA^2)).

Args: flow_rate_gpm: Flow rate in gallons per minute. mud_weight_ppg: Mud weight (ppg). tfa_sqin: Total flow area of nozzles (in^2).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flow_rate_gpmYes
mud_weight_ppgYes
tfa_sqinYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose assumptions, side effects, or limitations beyond the formula.

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 description is extremely compact, presenting the formula and parameter list in a well-organized manner with no wasted words.

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?

With an output schema present, the description need not detail return values; it includes the formula and parameter explanations, though missing potential assumptions or unit conventions.

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?

The description provides clear explanations for each parameter with units, compensating for the schema having no descriptions (0% coverage).

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 the tool calculates pressure drop across the bit using the given formula, distinguishing it from sibling calculation tools.

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 on when to use this tool versus alternatives; lacks context such as prerequisites or when the formula is applicable.

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