Skip to main content
Glama
petropt

petropt/petro-mcp

get_curve_values

Retrieve well log curves from LAS files, optionally filtering by depth range.

Instructions

Get specific curve data from a LAS file with optional depth range filtering.

Args: file_path: Absolute path to the LAS file. curve_names: List of curve mnemonics to retrieve (e.g., ["GR", "RHOB"]). start_depth: Optional start depth for filtering. end_depth: Optional end depth for filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
curve_namesYes
start_depthNo
end_depthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description does not disclose safety (e.g., read-only nature) or side effects beyond the basic operation.

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 with a clear Args section; every sentence adds value.

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?

Adequate for a data retrieval tool; explains parameters and optional filtering, though could mention file validity constraints.

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

Parameters5/5

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

Schema has 0% description coverage, but the tool description fully explains all 4 parameters, including optionality and an example for curve_names.

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?

Description clearly states the tool retrieves specific curve data from a LAS file with optional depth filtering, distinguishing it from siblings like get_curves and read_las.

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 this tool over alternatives like get_curves; lacks prerequisites or exclusions.

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