Retrieve the task tree for a specified project, including translated notification types and statuses. Requires prior selection of a project ID from the project list.
查询指定项目的任务树。调用本工具前必须先调用 queryProjProjectList 查询项目列表，并让用户选择正确的项目 id。工具会调用 /projTask/getTasksByProject 获取任务，组装为树形结构，并用 notify_type、proj_status 数据字典翻译通知类型和任务状态。
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | 项目ID。调用前先使用 queryProjProjectList 让用户选择正确项目。 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses internal API call, assembly into tree structure, and data dictionary translation. Without annotations, this provides good insight, though read-only nature is implied rather than explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, each adding value: purpose and usage guideline. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Explains internal steps and transformation, sufficient for a simple query tool. Lacks explicit output format description but mentions 'tree structure'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description already covers projectId with prerequisite info. Description adds no new semantic information beyond reinforcing the same guidance.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb (query) and resource (task tree of a project). It distinguishes from sibling tools like queryProjProjectList (list projects) and CRUD tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states prerequisite: must call queryProjProjectList first and let user select project ID. Provides clear step-by-step guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/guansuian/project-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server