Skip to main content
Glama
Sign In
ESP Input Bridge

ESP Input Bridge

by jensengao194-spec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stop

Idempotent

Ends the active input session and releases held keyboard and mouse inputs; restart the server to allow inputs again.

Instructions

Stop this session and release inputs; restart the server to permit inputs again.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

The annotations say readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds context the annotations do not provide: inputs are released and re-enabling input requires a server restart. That restart requirement is a non-obvious operational consequence and materially affects how an agent plans to use the tool.

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 sentence; the action comes first, followed by the consequence and the way to recover. No filler.

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 zero parameters, no output schema, and annotations already covering the safety profile, the description is nearly sufficient. Minor gaps remain: it does not state whether the stop is graceful or whether in-flight work is discarded.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description introduces no parameters and needs no parameter explanation.

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 scope: stop this session, plus the side effect of releasing inputs. It is clearly distinct from observe and act by implication, but never names those siblings to confirm the contrast.

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?

The terminal nature of the call and the recovery path (restart the server) are implied, so an agent can infer this is an end-of-work action. However, there is no explicit "use this instead of X" guidance relative to observe or act, nor any precondition for calling it.

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