Skip to main content
Glama

get_params

Read-onlyIdempotent

Retrieve a robot's navigation parameters and their allowed ranges by robot ID to validate limits before inspecting or controlling a simulated warehouse robot fleet.

Instructions

Navigation parameters of a robot with their allowed ranges.

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": {
      "robot_id": "<robot_id>"
    },
    "name": "get_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world, so the safety profile is fully covered without the description. The one added fact is that the payload contains allowed ranges rather than current values, which is genuinely useful context but thin beyond that.

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?

One short sentence with no wasted words and the key scope ('allowed ranges') placed at the end, but the brevity is under-specification rather than economy — it leaves the reader with a fragment instead of a statement of behavior.

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

Completeness4/5

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

placeholder

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

Parameters1/5

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

placeholder

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

Purpose3/5

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

The phrase names the resource ('navigation parameters') and its scope ('allowed ranges'), so an agent can infer this is a read of parameter bounds. However, it is a bare noun fragment with no verb, and it never distinguishes itself from set_param or from get_robot_state, which likely also surface parameter-like state.

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 or when-not-to-use guidance at all. Nothing tells the agent whether to call this instead of get_robot_state or in conjunction with set_param, so selection must be guessed 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.