Skip to main content
Glama
Sign In
Shrimp Task Manager

Shrimp Task Manager

by cjo4m06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

verify_task

Verify task completeness by ensuring all requirements and technical standards are met.

Instructions

全面驗證任務完成度，確保所有需求與技術標準都已滿足，並無遺漏細節

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": "verify_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes待驗證任務的唯一標識符，必須是系統中存在的有效任務ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It does not indicate whether the tool is read-only, modifies state, requires special permissions, or what happens upon failure. The phrase 'comprehensively verify' implies a check, but side effects or output behavior are not described.

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

Conciseness5/5

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

The description is one concise sentence that immediately conveys the tool's purpose. It is front-loaded with the verb 'verify' and the object 'task completion', with no wasted words.

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 absence of an output schema and annotations, the description should explain what the tool returns or any behavioral details. It does not mention whether it returns a boolean, a detailed report, or throws errors. For a verification tool, this lack of completeness leaves the agent guessing about the outcome.

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?

The input schema has 100% coverage with a single parameter 'taskId' documented as a UUID for a valid task ID. The description adds no further semantic value beyond the schema, so the baseline score of 3 is appropriate.

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 the tool's purpose: to comprehensively verify task completion, ensuring all requirements and technical standards are met. It uses a specific verb ('verify') and resource ('task'), and distinguishes itself from sibling tools like 'complete_task' (marking done) and 'analyze_task' (analysis).

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?

The description does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. For a verification tool, context on typical usage (e.g., after task execution) would be helpful but is absent.

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