Skip to main content
Glama
Sign In
wattsonic-modbus-docs

wattsonic-modbus-docs

Official
by WattsonicAdmin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_recipe

Retrieve a closed-loop control recipe by task ID or description, including preconditions, ordered Modbus steps, confirmation reads, and failure recovery—documentation only, no device access.

Instructions

A closed-loop control recipe: preconditions (with read checks), ordered steps (op read/write, address, function code, raw value or value range, check), confirmation reads with expected values, failure and recovery, notes and the documentation sections it is based on. Values are raw register values; negative values are sent as 16-bit two's complement. Documentation only; never touches a device.

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": {
      "task": "<task>"
    },
    "name": "get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesRecipe id (e.g. 'native.ems_session_start') or a task description (e.g. 'forced charge sunspec').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does real work by declaring 'Documentation only; never touches a device' and by explaining that values are raw register values with negatives as 16-bit two's complement — both genuinely useful behavioral facts. It stops short of stating what happens when the task string matches nothing (fuzzy match? error?) or whether lookups are case-sensitive, which matters given the free-text parameter.

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?

It is a single dense sentence fragment with no leading verb, front-loaded with the returned structure rather than the action. Every clause is informative — nothing is padding — but the list-of-fields format is harder to scan than a short lead sentence followed by detail.

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?

With one parameter and no output schema, the description must stand in for the return shape, and it does so thoroughly: preconditions, steps with op/address/function code/value/check, confirmation reads, failure/recovery, notes, and provenance. Only the free-text matching behavior of the task parameter is left unexplained.

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

Parameters3/5

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

Schema coverage is 100% and the schema already gives both examples ('native.ems_session_start' and 'forced charge sunspec'), so the description adds nothing parameter-specific. Baseline 3 applies since the schema carries the semantics.

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 enumerates what a recipe contains (preconditions, ordered steps, confirmation reads, failure/recovery, doc sections), so an agent knows exactly what resource it gets back, and the closing clause clarifies it is documentation, not device interaction. It never states a verb or explicitly contrasts with list_recipes, so the read-vs-browse distinction must be inferred from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the schema shows it accepts an id or a natural-language task description, which suggests 'look up the procedure you need.' There is no explicit when-to-use guidance, no mention of list_recipes for browsing, and no pointer to validate_write or get_register for the follow-up actions the recipe describes.

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