Skip to main content
Glama
Codex Team Workbench

Codex Team Workbench

by 912925635

team_get_request

Read-only

Reads one execution or host-action request with its stored instructions and required revisions, returning only that request instead of an entire board.

Instructions

Read one exact execution/host-action request with its stored instructions and required target/parent revisions. Returns no unrelated tasks, messages or work history. Use for compact panel requests instead of loading an entire board.

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>",
      "requestId": "<requestId>",
      "kind": "<kind>"
    },
    "name": "team_get_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
boardIdYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.6

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: it discloses the scope of the return payload (instructions, target/parent revisions) and, importantly, what is excluded (tasks, messages, work history). It omits error behavior when a requestId is not found, which keeps it from a 5.

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 with the core action front-loaded, then the exclusion scope, then the usage cue. Every sentence contributes, though the second sentence's exclusion list slightly overlaps with the first sentence's payload description.

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 simple 3-required-parameter read with no output schema, the description adequately covers what comes back and what does not. However, with zero schema coverage and no explanation of what a boardId represents or how the two 'kind' values differ in output, an agent still has to infer some calling details.

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 description coverage is 0%, so the description must carry parameter meaning, and it only partially does: 'execution/host-action' maps to the 'kind' enum and 'one exact ... request' implies requestId. boardId is never explained, and the phrase 'required target/parent revisions' describes returned data rather than any input, which could momentarily be mistaken for a parameter.

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?

The description gives a specific verb+resource: reading a single execution or host-action request, plus its stored instructions and required revisions. That is clearly more precise than the name alone, and the mention of both request kinds maps onto the 'kind' enum. It stops short of explicitly distinguishing itself from the similarly named sibling tools that record/request executions, leaving a small ambiguity an agent must resolve from names.

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?

"Use for compact panel requests instead of loading an entire board" gives a real when-to-use condition and points away from a heavier alternative (board/panel loading). Combined with "Returns no unrelated tasks, messages or work history," it tells the agent this is the narrow lookup path. It does not name the alternative tool explicitly or state when this tool should not be used (e.g., when requestId is unknown).

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