Skip to main content
Glama
Sign In
idm-mcp

idm-mcp

by Isotel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Idm List Parameters

idm_list_parameters

Lists a device's parameter paths without values, optionally filtered by prefix, so you can inspect the IDM gateway's configuration structure.

Instructions

List a device's parameter paths without their values.

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": {
      "device": "<device>"
    },
    "name": "idm_list_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYesroot, full name or unambiguous substring.
prefixNorestrict to paths starting with this prefix, e.g. "ec/ChA".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. 'List ... without their values' usefully characterizes the payload as paths only and implies a read-only operation, but there is no statement about permissions, error behavior on ambiguous substrings, or result size/pagination limits.

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?

A single tight sentence with no filler, and the distinguishing qualifier ('without their values') is positioned at the end where it does the most differentiating work. Nothing needs trimming or front-loading.

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?

For a two-parameter read-only listing tool with 100% schema coverage and an output schema (so return values need no explanation), the description is nearly sufficient. The remaining gap is routing guidance relative to idm_get_parameters/idm_get_value, which an agent must infer from the phrase 'without their values'.

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 description coverage is 100%: `device` (root, full name, or unambiguous substring) and `prefix` (path-prefix restriction, with example) are both documented in the schema. The description adds nothing about either parameter, so the baseline of 3 applies.

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 ('List') and resource ('a device's parameter paths'), plus the key scope modifier 'without their values', which implicitly contrasts it with the sibling idm_get_parameters. It is clear what the tool returns, though it never names the sibling it differs from.

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: an agent can infer this is the lightweight option when values are not needed, since 'without their values' contrasts with a values-returning sibling. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of how ambiguity in the `device` substring is handled.

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