Skip to main content
Glama

Coline

Read who has a task and where it stands

read_task_state
Read-onlyIdempotent

One line: who is working it and where it stands ("Ada is on it", "Claude Code, for Radin: opening the change request", "With Acme. Sent Nov 12. Due Friday.", "Waiting on Sam", "Starts after ENG-12").

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>"
    },
    "name": "read_task_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
stateLineYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description's added value is disclosing that the response is deliberately terse — one line — which helps an agent decide whether it needs a richer read, but it says nothing about scope of ownership resolution, staleness, or what happens when nothing is set.

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?

A single front-loaded sentence followed by illustrative examples; nothing is buried and there is no filler. The five examples are slightly more than strictly needed, but each demonstrates a distinct status shape (person, agent, external party, waiting, dependency), so they largely earn their place.

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?

An output schema exists, so the description need not document return values, and the annotations cover safety. However, with three required parameters and two undocumented in the schema, plus no routing guidance among many read_* siblings, the definition leaves real gaps for an agent choosing and calling it.

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 only 33%: only the workspace slug is documented, while taskId and taskboardId are bare strings. The description says nothing about any of the three parameters, so it fails to compensate for the uncovered ones; an agent must infer that taskId identifies the task whose state is summarized.

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 states what the tool surfaces: a single line naming the owner and the current status of a task, made concrete by examples like "Ada is on it" and "With Acme. Sent Nov 12. Due Friday." An agent can tell this is a compact status summary rather than a full record, though it never uses an explicit verb ("returns") or names a sibling such as get_task or read_task_view to sharpen the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when this tool is the right choice versus read_task_view, get_task, read_task_history, or read_waiting_on, all of which plausibly overlap. The description implies light-weight status checking but never states prerequisites, exclusions, or the conditions that select this tool over its siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources