Skip to main content
Glama
gabrielserrao

pyResToolbox MCP Server

get_component_properties

Retrieve critical hydrocarbon component properties for compositional analysis and EOS calculations from a comprehensive petroleum engineering database.

Instructions

Get critical properties for hydrocarbon components from database.

COMPONENT DATABASE - Access to comprehensive database of critical properties for standard hydrocarbon components and common non-hydrocarbons. Essential for compositional analysis, EOS calculations, and phase behavior modeling.

Parameters:

  • component (str, required): Component name. Case-insensitive. Examples: "methane", "C1", "ethane", "C2", "propane", "C3", "n-butane", "nC4", "i-butane", "iC4", "benzene", "toluene", "N2", "CO2", "H2S", "H2O".

  • eos (str, optional, default="PR79"): Equation of State model. Options: "PR79", "PR77", "SRK", "RK". PR79 recommended.

Available Components:

  • Light Ends: Methane (C1), Ethane (C2), Propane (C3), Butane (C4), Pentane (C5)

  • Normal Paraffins: n-C4 through n-C45 (n-butane to n-pentatetracontane)

  • Branched Alkanes: iC4 (isobutane), iC5 (isopentane), neoC5 (neopentane)

  • Aromatics: Benzene (C6H6), Toluene (C7H8), Xylenes (C8H10)

  • Naphthenes: Cyclopentane, Cyclohexane

  • Non-Hydrocarbons: N2 (nitrogen), CO2 (carbon dioxide), H2S (hydrogen sulfide), H2O (water)

Properties Returned:

  • MW: Molecular weight in lb/lbmol. Example: 16.04 for methane.

  • Tc: Critical temperature in °R. Example: 343.0 for methane.

  • Pc: Critical pressure in psia. Example: 667.8 for methane.

  • Zc: Critical compressibility factor (dimensionless). Example: 0.286 for methane.

  • Omega: Acentric factor ω (dimensionless). Example: 0.011 for methane.

  • Vcritical: Critical volume in cuft/lbmol. Example: 1.59 for methane.

  • Tb: Normal boiling point in °R. Example: 201.6 for methane.

  • SG: Specific gravity (dimensionless, relative to water). Example: 0.554 for methane.

EOS Models:

  • PR79 (Peng-Robinson 1979): RECOMMENDED. Most widely used, best accuracy. Use for: Most applications, hydrocarbon systems, gas processing.

  • PR77 (Peng-Robinson 1977): Original version. Use for: Compatibility, older models.

  • SRK (Soave-Redlich-Kwong 1972): Alternative EOS. Use for: Specific applications, comparison.

  • RK (Redlich-Kwong 1949): Older EOS. Use for: Historical compatibility, simple systems.

Critical Properties Usage: Critical properties are essential for:

  • EOS phase behavior calculations (PR, SRK, RK)

  • Flash calculations (bubble point, dew point)

  • Phase envelope generation

  • Compressibility factor calculations

  • Vapor-liquid equilibrium

Applications:

  • Compositional Simulation: Input component properties for compositional models

  • EOS Phase Behavior: Calculate phase envelopes and phase boundaries

  • Flash Calculations: Solve vapor-liquid equilibrium problems

  • PVT Modeling: Build compositional PVT models

  • Gas Processing Design: Design separation and processing facilities

  • Material Balance: Compositional material balance calculations

Source: Industry-standard component database with properties from:

  • NIST (National Institute of Standards and Technology)

  • API (American Petroleum Institute) data

  • EOS calibrations and literature values

Returns: Dictionary with:

  • component (str): Component name

  • eos_model (str): EOS model used

  • properties (dict): All critical properties (MW, Tc, Pc, Zc, Omega, Vcritical, Tb, SG)

  • method (str): "Component database lookup"

  • note (str): Usage guidance

  • inputs (dict): Echo of input parameters

Common Mistakes:

  • Component name misspelled (check spelling, try common aliases like "C1" for methane)

  • Wrong EOS model (use PR79 unless specific requirement)

  • Case sensitivity (component names are case-insensitive, but use standard capitalization)

  • Component not in database (check available components list)

  • Using properties from wrong EOS (properties are EOS-specific)

Example Usage:

{
    "component": "methane",
    "eos": "PR79"
}

Result: Returns all critical properties for methane calibrated for PR79 EOS.

Note: Component properties are EOS-specific. Always use properties from the same EOS model throughout your calculations. PR79 is recommended for most applications. For components not in database, use external sources or estimate from correlations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description carries the full burden and excels by disclosing key behavioral traits. It details the database source (NIST, API), explains that properties are EOS-specific, warns about common mistakes (e.g., misspellings, wrong EOS), and provides usage guidance (e.g., PR79 recommended). This goes beyond basic functionality to include operational context and limitations.

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

Conciseness3/5

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

The description is front-loaded with the core purpose but includes extensive sections (e.g., 'Available Components,' 'EOS Models,' 'Applications') that, while informative, could be streamlined. Some sentences, like detailed lists of components, may not all earn their place for conciseness, though the structure is organized with headings for clarity.

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

Completeness5/5

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

Given the tool's complexity (database lookup with EOS-specific properties), no annotations, and an output schema present, the description is highly complete. It covers purpose, parameters, returned properties, usage scenarios, common mistakes, examples, and notes, providing all necessary context for an AI agent to use the tool effectively without relying on structured fields.

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 description coverage is 0%, so the description must compensate fully. It does so by elaborating on both parameters: for 'component,' it provides examples, notes case-insensitivity, and lists available components; for 'eos,' it explains options, default, and recommendations. This adds significant meaning beyond the bare schema, ensuring parameters are well-understood.

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's purpose: 'Get critical properties for hydrocarbon components from database.' It specifies the verb 'Get' and the resource 'critical properties for hydrocarbon components,' distinguishing it from sibling tools like 'gas_critical_properties' or 'oil_twu_critical_properties' by focusing on a database lookup for compositional analysis rather than calculations or specific fluid types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use this tool, such as for 'compositional analysis, EOS calculations, and phase behavior modeling,' and lists applications like 'Compositional Simulation' and 'Flash Calculations.' However, it does not explicitly state when not to use it or name specific alternatives among sibling tools, though it implies alternatives for components not in the database.

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/gabrielserrao/pyrestoolbox-mcp'

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