Skip to main content
Glama
Sign In
Shrimp Task Manager

Shrimp Task Manager

by cjo4m06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

analyze_task

Analyze task requirements and codebase to assess technical feasibility and risks, outputting pseudocode for core implementation. Refine iteratively using previous analysis.

Instructions

深入分析任務需求並系統性檢查代碼庫，評估技術可行性與潛在風險，如果需要提供程式碼請使用 pseudocode 格式且盡量精簡只保留核心實現部分

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": {
      "summary": "<summary>",
      "initialConcept": "<initialConcept>"
    },
    "name": "analyze_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYes結構化的任務摘要，包含任務目標、範圍與關鍵技術挑戰，最少10個字符
initialConceptYes初步解答構想，包含技術方案、架構設計和實施策略，如果需要提供程式碼請使用 pseudocode 格式且盡量精簡只保留核心實現部分，最少50個字符
previousAnalysisNo前次迭代的分析結果，用於持續改進方案（僅在重新分析時需提供）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions systematic codebase checking and risk evaluation but does not disclose any behavioral traits such as side effects, required permissions, or state changes. The agent learns the tool's function but not its operational impact.

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

Conciseness3/5

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

The description is a single sentence that combines purpose and a usage note. It is adequately concise but not front-loaded; the pseudocode instruction could be separate. No wasted words, but structure could be improved.

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?

Given no output schema, the description should clarify what the tool returns. It mentions analysis and codebase checking but does not specify output format. The parameter details are covered by schema. Completeness is adequate but missing return value behavior.

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%, so the schema already documents all parameters. The description adds no new meaning beyond the schema, except repeating the pseudocode hint. Baseline score of 3 is appropriate as the schema handles parameter semantics.

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 clearly states the tool's action: analyzing task requirements, checking codebase, evaluating feasibility and risks. It uses specific verbs like '分析' and '檢查', and it distinguishes from siblings by focusing on analysis and risk assessment, though it could be more explicit.

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 provides a guideline to use pseudocode format for code output, but it does not specify when to use this tool instead of siblings like plan_task or reflect_task. There is no explicit context or exclusions.

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