Skip to main content
Glama
yusong652

itasca-mcp

by yusong652
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itasca_browse_reference

Browse ITASCA reference documentation by engine to find model properties, range filter syntax, and plot item configuration. Navigate categories or full paths for setup details.

Instructions

Browse ITASCA reference documentation (syntax elements, model properties).

Works across engines via the required software selector (pfc/flac/3dec). References are language elements used within commands, not standalone commands.

Navigation levels:

  • No topic: All reference categories for the engine

  • Category (e.g., "constitutive-models"): List items in category

  • Full path (e.g., "constitutive-models mohr-coulomb"): Full documentation

  • Sub-item path (e.g., "plot-items zone contour"): Sub-item details

When to use:

  • Need material/contact/joint model property names (kn, ks, fric, cohesion, friction, ...)

  • Need range filtering syntax (position, cylinder, group, id)

  • Need plot item configuration (contour, label, color-by, cut, transparency, legend)

  • Setting up model-assignment commands (e.g. "... cmodel assign ... property ...")

  • Using range filters in any command

  • Configuring "plot item create" commands

Related tools:

  • itasca_browse_commands: Command syntax (e.g., "zone create")

  • itasca_query_command: Search commands by keywords

Input Schema

NameRequiredDescriptionDefault
topicNoReference topic to browse (space-separated path). Categories vary by engine — call with no topic first to discover them. Examples (by engine): - None or '': List all reference categories for the chosen engine - PFC 'contact-models' / 'contact-models linear': contact model + its properties - FLAC 'constitutive-models' / 'constitutive-models mohr-coulomb': zone model + properties - 3DEC 'joint-models' / 'joint-models mohr': joint (sub-contact) model + properties - 'range-elements' / 'range-elements cylinder': range filter syntax (all engines) - 'plot-items' / 'plot-items <type>' / 'plot-items <type> <sub>': plot item keywords
versionNoDocumentation version (PFC: 6.0/7.0/9.0, FLAC: 7.0/9.0). Only gates version-specific items (e.g. PFC contact models by availability). range-elements, plot-items, and the FLAC/3DEC reference sets are version-agnostic, so the value is ignored for them. 9.0-only engines (MPoint, MassFlow) always resolve at 9.0.7.0
softwareYesITASCA engine to query: 'pfc', 'flac', '3dec', 'mpoint', or 'massflow'. Required — there is no default engine.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations, so the description carries the burden: it discloses that references are not standalone commands, that behavior varies by the required software selector, and details the four navigation levels (no topic, category, full path, sub-item). It does not discuss access requirements or return payload, though an output schema exists.

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?

Front-loaded with purpose, then structured navigation levels, when-to-use, and related tools. Some redundancy: plot-items and range examples appear both in navigation levels and in the when-to-use bullets, and the category example 'constitutive-models' conflicts with the PFC contact-models naming, adding minor noise.

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?

An output schema exists and all three parameters are fully described in schema. Combined with the description's navigation model, engine selector explanation, and when-to-use guidance, an agent has everything needed to call this correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already documents topic path formats, version gating, and the software enum with examples. The description's navigation-level list reinforces the topic parameter's semantics but largely restates what the schema provides, so baseline 3 is appropriate.

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?

Specific verb+resource: browse ITASCA reference documentation for syntax elements and model properties. The description also explicitly distinguishes references from commands ('References are language elements used within commands, not standalone commands'), separating it from itasca_browse_commands.

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

Usage Guidelines5/5

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

Provides an explicit 'When to use' list of concrete tasks (model property names, range filtering syntax, plot item config, cmodel assignment) plus a 'Related tools' section naming itasca_browse_commands and itasca_query_command with their distinct roles. Nothing left to inference.

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

Deploy Server

Other Tools