Skip to main content
Glama

List variables

list_variables
Read-only

Lists model inputs and outputs with units, shape, description, and current value, so you can inspect variables and filter by kind or name.

Instructions

List model inputs and/or outputs with units, shape, description and current value.

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": "list_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoboth
problem_idYes
name_filterNo
max_variablesNo
promoted_onlyNo

Output Schema

NameRequiredDescriptionDefault
errorNo
truncatedNo
variablesNo

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?

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that entries carry units/shape/description/value, but omits behaviorally important traits: promoted_only defaults to true (so unpromoted variables are silently hidden) and max_variables defaults to 200, with no statement about truncation or pagination when the cap is hit.

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 front-loaded sentence with no filler, and the returned fields are listed compactly. Its brevity is efficient rather than padded, though it tips into under-specification that other dimensions penalize.

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

Completeness2/5

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

For a 5-parameter tool with 0% schema coverage and non-obvious defaults (promoted_only=true, max_variables=200), the description covers almost none of what an agent needs. The output schema means return values need not be described, but nothing explains the silent filtering or caps.

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% across 5 parameters, so the description must carry the burden and does not: kind ('inputs'/'outputs'/'both'), name_filter, promoted_only, and max_variables are never explained. Only the inputs/outputs distinction is faintly echoed by phrasing, leaving the two filtering parameters and the cap undocumented.

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+resource ('List model inputs and/or outputs') and even enumerates what each entry carries (units, shape, description, current value). It does not differentiate itself from sibling readers such as get_outputs or get_problem_spec, so an agent cannot tell from the description alone which reader to pick.

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 when-to-use guidance, no exclusions, and no named alternative: siblings get_outputs and get_problem_spec plausibly overlap, yet the description never says which situation selects this tool. At best usage is implied by the word 'List'.

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