Skip to main content
Glama
Codex Team Workbench

Codex Team Workbench

by 912925635

team_request_host_action

Records a user-requested exact-target navigation or supported resume for a team member, without executing the host action or treating an acknowledgment as success.

Instructions

Record a user-requested exact-target navigation or supported continuation. Does not execute the host operation. A message acknowledgment is not success.

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": {
      "boardId": "<boardId>",
      "memberId": "<memberId>",
      "kind": "<kind>"
    },
    "name": "team_request_host_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
boardIdYes
memberIdYes
instructionsNo
expectedNativeIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.6

TDQS

B3.2/5.0
Behavior3/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world write. The description usefully discloses that no host action is actually performed and that an acknowledgment is not success — genuinely beyond the annotations — but it never explains what the record means, who consumes it, or that the request must be fulfilled by a separate step (e.g. team_record_host_action).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and its key limitation. 'A message acknowledgment is not success' is terse to the point of being cryptic without surrounding context, but nothing is padded.

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?

For a 5-parameter mutation tool with no output schema and zero parameter documentation, the description covers the most consequential behavior (non-execution) but leaves the return/record lifecycle and all parameter meanings unaddressed. Adequate minimally, with clear gaps.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must compensate and does not. Only 'exact-target' loosely hints at expectedNativeId; kind's 'navigate'/'resume' enum, instructions, boardId and memberId receive no semantic explanation anywhere.

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 ('Record') and a specific object ('a user-requested exact-target navigation or supported continuation'), and immediately clarifies it is not execution. This differentiates it from action-executing siblings in spirit, though no sibling is named, so an agent must infer how it differs from team_record_host_action or team_append_record.

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 description implies 'use this to log an intent before/without acting' via 'Does not execute the host operation', and warns that 'a message acknowledgment is not success'. It gives no explicit when-to-use vs. when-to-use-alternatives routing against the many team_* record/request siblings, leaving selection to inference.

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