Skip to main content
Glama
Sign In
Shrimp Task Manager

Shrimp Task Manager

by cjo4m06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_task_detail

Retrieve complete task details including full implementation guides and verification standards using a task ID.

Instructions

根據任務ID獲取任務的完整詳細信息，包括未截斷的實現指南和驗證標準等

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes欲檢視詳情的任務ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It hints at providing untruncated data (implying other tools may truncate), but does not state read-only nature, permissions, or rate limits. Adequate for a simple read operation but lacks explicit behavioral details.

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 front-loads the action and resource. In Chinese, concise but could be restructured for better readability. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description covers expected content (full details, implementation guide, verification standards). Could specify additional fields like status or timestamps, but sufficient for a get-detail tool among many siblings.

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

Parameters4/5

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

Schema coverage is 100% with parameter description '欲檢視詳情的任務ID'. The description adds context about what the returned details include (implementation guide, verification standards), providing value beyond the schema.

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 action (獲取) and resource (任務的完整詳細信息), and specifies what includes (未截斷的實現指南和驗證標準). It distinguishes from siblings like list_tasks and update_task.

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

Usage Guidelines3/5

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

The description implies usage when needing full task details including implementation guides, but does not explicitly state when to use vs alternatives like list_tasks or query_task. No exclusions or prerequisites mentioned.

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