Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Stop simulator

sim_stop

Stops this server's simulator sessions and waits for port 1234 to close, recovering a wedged simulator. Set force to true, only with user approval, to stop a simulator started by someone else.

Instructions

Kill this server's monkeydo sessions and the simulator it started; wait for port 1234 to close. Recovers a wedged simulator. Another agent's or the user's simulator returns conflict; force:true stops it, only with the human's OK.

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": "sim_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoalso stop a simulator this server did not start (another agent's or the user's); only after the human agreed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile, and the description adds behavior they cannot: a blocking wait until port 1234 closes, and typed conflict behavior based on simulator ownership with an explicit human-consent gate for force. What is not explained is the outcome when no simulator is running (the annotations mark idempotentHint=false but the description never says whether that case errors or is a no-op).

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?

Three dense sentences, front-loaded with the action and scope before the conflict and override rules, with no filler wording to trim.

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 single-parameter stop tool with annotations and no output schema, the definition covers scope, blocking behavior, conflict semantics, and the consent gate. The only meaningful omission is the no-op or error case when no simulator exists.

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 force parameter already carries a full description including the human-approval condition, so the description only restates it as 'only with the human's OK'. That is consistent but adds no meaning 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?

Specific verb plus resource: it kills this server's monkeydo sessions and the simulator it started, and it names the exact scope boundary ('this server's') that separates it from sim_run and other sim_* siblings. The stated side effect (waiting for port 1234 to close) makes the operation unambiguous.

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 gives the use case ('Recovers a wedged simulator') and the exclusion with its remedy: a simulator owned by another agent or the user returns conflict, and force:true overrides it only with human approval. The when, when-not, and escalation condition are all stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.