Skip to main content
Glama
Sign In
PatchWarden

PatchWarden

by jiezeng2004-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_test_log

Fetch the test log for a given task, or if the log is not ready, obtain structured availability details and watcher evidence.

Instructions

Read test.log, or return structured availability and watcher evidence while it is not ready.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_test_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

C2.4/5.0
Behavior2/5

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

Without annotations, the description must fully disclose behavior. It mentions a dual-mode behavior (read log vs return evidence) but does not explain the conditions, side effects, or required permissions. The behavioral traits are inadequately described.

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

Conciseness2/5

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

The description is extremely concise (one sentence) but is unclear and under-specified. The phrasing 'while it is not ready' introduces confusion without earning its place. Conciseness alone does not compensate for lack of clarity.

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?

Given the conditional behavior and lack of output schema, the description is incomplete. It does not explain what 'structured availability and watcher evidence' means, when each mode triggers, or the return format. Essential context is missing.

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 coverage is 100% for the single parameter, so the baseline is 3. The description does not add any meaning beyond the schema's 'Task ID' label. No extra semantics are provided.

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 description specifies 'Read test.log' which indicates a resource, but the conditional clause 'or return structured availability and watcher evidence while it is not ready' is ambiguous and unclear. It does not clearly differentiate from sibling tools like get_task_log_tail or get_result.

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 is provided on when to use this tool versus siblings such as get_task_log_tail, get_result, or others. The description lacks context about prerequisites or alternatives.

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