Skip to main content
Glama
Sign In
Itential MCP Server

Itential MCP Server

Official
by itential
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Start Adapter

start_adapter
Destructive

Start a stopped adapter on Itential Platform and wait until it reaches running state; raises an error for dead or deleted adapters.

Instructions

Start an adapter on Itential Platform.

Behavior based on current adapter state:

  • RUNNING: No action taken (already started)

  • STOPPED: Attempts to start and waits for RUNNING state

  • DEAD/DELETED: Raises InvalidStateError (cannot start)

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the adapter to start
timeoutNoTimeout waiting for adapter to start

Output Schema

NameRequiredDescriptionDefault
nameYesThe name of the adapter
stateYesOpreational state (DEAD, STOPPED, RUNNING, DELETED)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the annotations by detailing exact behavior per adapter state: no action for RUNNING, attempts start and waits for STOPPED, and raises InvalidStateError for DEAD/DELETED. This adds significant context about side effects and error conditions.

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?

The description is succinct and well-structured, using a concise opening line followed by a bullet-point list for state behaviors. Every sentence adds distinct value 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?

The description fully covers the tool's behavior for all relevant adapter states, including error handling. With an output schema present and a simple two-parameter input, the description provides complete context for invocation.

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?

The input schema already covers both parameters (name and timeout) with clear descriptions, so the schema coverage is 100%. The description does not add additional parameter semantics beyond the schema, warranting the baseline score.

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 opens with 'Start an adapter on Itential Platform,' which is a specific verb plus resource. It clearly distinguishes from sibling tools like stop_adapter and restart_adapter by focusing on the start action and describing state-dependent behavior.

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

Usage Guidelines4/5

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

The state-based behavior provides clear context for when this tool is applicable: it is effective for STOPPED adapters, a no-op for RUNNING, and an error for DEAD/DELETED. However, it does not explicitly mention alternatives or when not to use it, so it lacks full exclusion guidance.

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