Skip to main content
Glama

Get problem spec

get_problem_spec
Read-only

Retrieves the stored ProblemSpec for a given problem ID so you can inspect or reuse its declarative OpenMDAO model definition.

Instructions

Return the stored ProblemSpec of a problem.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "problem_id": "<problem_id>"
    },
    "name": "get_problem_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
problem_idYes

Output Schema

NameRequiredDescriptionDefault
specNo
errorNo
problem_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a non-mutating read, so the description only needs to add context. The word 'stored' usefully implies retrieval of persisted state rather than a computed spec, but nothing is said about behavior when the problem is unloaded or the id is unknown. With return values covered by the output schema, this is adequate but thin.

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?

A single short sentence with no filler and the resource front-loaded. It is efficient, though so terse that brevity comes at the cost of information rather than from tight editing.

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?

The tool is a simple single-parameter read and an output schema exists, so return values need not be described. Still, the definition omits any error behavior or hint about obtaining a valid problem_id, leaving gaps an agent would want filled for a lookup-style tool.

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 carry the burden for problem_id and does not — it never says what the id refers to, where to obtain it, or how the pattern constraint matters. The regex in the schema hints at format, but no semantic meaning is added.

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?

States a specific verb (return) and resource (the stored ProblemSpec of a problem), so an agent knows this is a read of an existing specification. It does not differentiate from siblings such as get_outputs or list_problems, and 'ProblemSpec' is unexplained domain jargon, but the action itself is unambiguous.

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?

There is no guidance on when to use this versus alternatives like get_outputs, list_problems, or query_cases, and no prerequisites stated. The agent must infer usage from the name alone.

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