Skip to main content
Glama
lira-sapr-mcp

lira-sapr-mcp

by EvgenVer

lira_periods

Read-only

Retrieve modal periods, frequencies, modal and accumulated masses, and participation factors for specified dynamic load cases in a LIRA model to review dynamic response data.

Instructions

Modes of the dynamic load cases (default all): per mode the period (s), frequency (Hz and rad/s), modal mass and accumulated modal mass (% of the total) and participation factor; "type" is LIRA's dynamic load type code (e.g. 35, 100).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lira_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
load_casesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context about the returned modal quantities and the default-all behavior, but does not cover prerequisites, permissions, or output format beyond what the output schema likely provides.

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 a single front-loaded sentence, but much of it enumerates return fields that are already covered by the output schema, reducing focus on invocation semantics.

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

Completeness3/5

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

Because an output schema exists and readOnlyHint is present, the description does not need to explain return values in depth. However, it leaves gaps around the model parameter and the practical context for invoking the tool, so it is only adequate rather than complete.

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

Parameters2/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 for both parameters. It only hints that load cases default to all and fails to explain the model parameter or accepted load case values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as modes/periods of dynamic load cases and states the default scope is all load cases. It lacks an explicit action verb and does not differentiate itself from sibling result-extraction tools, but the purpose is still understandable.

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?

The only usage guidance is that load cases default to all. There is no indication of when to use this tool versus related result tools, nor any prerequisite such as running a dynamic analysis first.

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