Skip to main content
Glama
Sign In
ESP RainMaker MCP Server

ESP RainMaker MCP Server

Official
by espressif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_params

Retrieve the current parameters or state of a specific device node. Use this to obtain up-to-date values without additional device details.

Instructions

Get ONLY the current parameters (state) for a specific node.

Use this tool only when:

  • User specifically asks for "parameters", "state", or "current values" of a particular device

  • You already have other info and need just the current state

For comprehensive device information, use get_node_details instead.

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

Input Schema

NameRequiredDescriptionDefault
node_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided; the description implies a read operation by saying 'get' but does not explicitly state it is non-destructive or safe. It focuses on scope and purpose but lacks behavioral details like auth or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise: a single short paragraph with the core action upfront, followed by usage guidelines. Every sentence serves a purpose with no redundancy.

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?

Given the tool's simplicity (one parameter, read operation, output schema exists), the description covers purpose, usage guidance, and differentiation from siblings. No missing critical information.

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 coverage is 0% and the description adds no extra detail about the node_id parameter (e.g., format, source, expected values). It merely rephrases 'specific node' from the tool name, adding little value beyond the schema.

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?

The description clearly states the tool retrieves current parameters/state for a specific node, distinguishing it from the sibling tool get_node_details by emphasizing it provides only state information.

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?

Explicitly defines when to use the tool (user asks for parameters/state/current values, already have other info) and when not to use it (for comprehensive info, use get_node_details), with clear alternatives.

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