Skip to main content
Glama
Sign In
deepwork

deepwork

by saisharan0103
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read task status

task_status
Read-onlyIdempotent

Retrieve the append-only evidence state and current quality-gate stage for a task to verify completion.

Instructions

Return the append-only evidence state and current quality-gate stage for a task.

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": {
      "taskId": "<taskId>"
    },
    "name": "task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's mention of 'append-only' aligns but does not add new behavioral context beyond what annotations provide.

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?

Single sentence that is front-loaded with the verb. Efficient but omits essential parameter explanation, slightly reducing effectiveness.

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?

Missing description of the return value structure and parameter details. Annotations cover safety, but for a read operation with no output schema, the description should explain the output format.

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

Parameters1/5

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

Schema coverage is 0% and the description does not document the `taskId` parameter at all, leaving the agent without guidance on valid values, format, or constraints despite the schema having a pattern.

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 it returns the 'append-only evidence state' and 'current quality-gate stage' for a task, specifying the verb and resource. It distinguishes from siblings like final_gate by describing the precise components returned.

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?

No guidance on when to use this tool versus alternatives like final_gate or inspect_repository. No indications of preconditions or when not to use it.

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