Skip to main content
Glama
kitepon

aiterm-mcp

by kitepon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

agent_steer

Inject additional messages into a running Codex or Grok agent to steer its current turn. Returns idle status when the agent is inactive, preventing new-turn starts.

Instructions

実行中のCodex/Grok agentへ追加メッセージを差し込み、現在のターンを誘導する。独立した次ターンを始める用途ではなく、idle時は文字を送らずdelivery=idleを返す。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes現在のターンへ追加する文字列。UTF-8で最大64KiB
imageNo添付する画像ファイルの絶対パス（png/jpg/jpeg/gif/webp）
session_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYes
vendorYes
harnessYes
deliveryYes
launch_idYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.31.2
    • addedInput schema / properties / image
      Added value: +{
+  "description": "添付する画像ファイルの絶対パス（png/jpg/jpeg/gif/webp）",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Addedv0.29.21

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose an important edge-case behavior (idle delivery returns delivery=idle without sending text), which adds value beyond the schema. However, it does not describe the return behavior for the normal case, potential side effects, or permission requirements, leaving gaps for a mutating 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?

The description is two sentences with no filler: the first states the core purpose and the second addresses a critical exception. The information is front-loaded and every clause adds value, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately complex with three parameters and no output schema or annotations. The description explains the idle case but leaves out the normal-case return value, error behavior, and any permissions or prerequisites. Given the lack of output schema, more detail on expected responses would make it more complete.

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 provides descriptive text for the text and image parameters, including UTF-8 and max size for text and file types for images. The description adds minimal extra semantic nuance beyond labeling the action as 'adding a message to the current turn,' which is already implied by the schema. Thus it stays near the baseline for high schema coverage.

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 clearly states the tool's function with a specific verb ('差し込み' / inject) and resource ('実行中のCodex/Grok agent'), and it specifically clarifies that it steers the current turn rather than starting a new one. This distinguishes it from potential sibling tools even without naming any.

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 description gives clear usage context: it is for adding to an ongoing turn, not for initiating an independent next turn. It also instructs that when the agent is idle no text should be sent and delivery=idle is returned, which guides when to call vs. avoid. It does not name alternative tools, but none are provided, so this is reasonably complete.

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