Skip to main content
Glama
Codex Team Workbench

Codex Team Workbench

by 912925635

team_record_host_action

Records a host action result against a workbench board action using its actual source, so teams can track delivery, acknowledgment, success, failure, or cancellation accurately.

Instructions

Record one exact supported host result with its actual source. ui/open-link acknowledgment is accepted, not visual success; ui/message delivery alone cannot succeed. User-confirmed cancelled only closes the local workbench wait and never sends a message or stops a native operation.

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>",
      "actionId": "<actionId>",
      "expectedRevision": "<expectedRevision>",
      "nativeId": "<nativeId>",
      "status": "<status>",
      "source": "<source>",
      "result": "<result>"
    },
    "name": "team_record_host_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultYes
sourceYes
statusYes
boardIdYes
actionIdYes
nativeIdYes
confirmedNo
expectedRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.6

TDQS

B3.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries the real behavioral burden and mostly does: it clarifies that a cancellation is purely local (never sends a message, never stops a native operation) and that an open-link acknowledgment is not visual success. That is substantive beyond the annotations, though it never states persistence or idempotency behavior for the recorded entry.

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 tight sentences with no filler, and the core action is stated first with the exception rules following. The ellipsis in the opening sentence ('one exact supported host result') slightly hurts readability but nothing is redundant.

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

Completeness2/5

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

For an 8-parameter, 7-required mutation tool with zero schema coverage and no output schema, the description should explain the revision/concurrency parameter, how boardId/actionId/nativeId relate, and what `confirmed` gates. Instead it covers only status/source corner cases, leaving most of the call contract undocumented.

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 8 parameters, so the description must compensate and it largely does not. It adds meaning for a few source/status values (ui/open-link, ui/message, panel-user-confirmation, accepted, cancelled) but says nothing about boardId, actionId, nativeId, expectedRevision, confirmed or result, including the optimistic-concurrency implication of expectedRevision.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Record' plus 'host result' gives a rough idea, and 'with its actual source' signals the source field matters. But 'one exact supported host result' is vague phrasing, and there is no differentiation from siblings like team_record_execution, team_record_workflow or team_append_record, which an agent would need to pick among.

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?

Usage is only implied: you record a host action's outcome after one occurs. The description does give rule-like guidance for specific cases (ui/open-link acknowledgment is accepted, ui/message delivery alone cannot succeed, user-confirmed cancelled only closes the local wait), which steers status/source selection. It never states explicitly when to choose this tool over the other team_record_* tools.

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