Skip to main content
Glama
Sign In
idm-mcp

idm-mcp

by Isotel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Idm Get Streams

idm_get_streams

List TCP streams exposed by an ISOTEL IDM gateway, including names and optional device filtering. De-duplicate streams across devices that share one connection port.

Instructions

List the TCP streams the gateway exposes, with their names.

De-duplicated across devices that share one connection port.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "idm_get_streams"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNorestrict to one device (root, name or substring); omit for all.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 carries the full behavioral burden. 'List' implies a safe read and the de-duplication rule across devices sharing a connection port is a genuine behavioral disclosure beyond the schema. However, it says nothing about permissions, result size, or whether the listing is live or cached.

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?

Two short sentences with zero filler. The primary purpose is front-loaded and the de-duplication caveat follows it naturally.

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?

An output schema exists, so return values needn't be explained, and the one optional parameter is fully covered by the schema. The definition is nearly complete for a simple filtered list; only the relationship to idm_read_stream is left unstated.

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 single optional 'device' parameter is fully documented in the schema (root, name or substring; omit for all). The description adds no parameter detail, so the baseline 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 and resource ('List the TCP streams the gateway exposes') and adds the shape of the result ('with their names'). The de-duplication clause further defines scope, though it never names the confusable sibling idm_read_stream, which an agent must disambiguate on its own.

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?

No when-to-use or when-not guidance. The agent is not told to call this instead of idm_read_stream when it wants metadata rather than stream content, nor when to prefer idm_get_protocols or idm_list_connections. Usage must be inferred 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.

Deploy Server

Other Tools