Skip to main content
Glama
Sign In
Dida365 MCP Server

Dida365 MCP Server

by Martinqi826
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_project_detail

Retrieves detailed information about a Dida365 project including all its tasks. Provide the project ID to access project data and task list.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes项目ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 full burden. It states the tool retrieves information but does not explicitly confirm it is read-only, specify error behavior for missing project_id, or disclose any rate limits or side effects. More behavioral context is needed.

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 a single sentence with no unnecessary words. It efficiently conveys the purpose and scope without redundancy.

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?

For a simple get tool with one parameter and no output schema, the description adequately states the function. However, it could improve by clarifying how the output differs from combining get_projects and get_all_tasks, and by noting if any filtering or pagination applies.

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% description coverage for the single parameter 'project_id'. The description adds no extra semantics beyond the schema, such as expected format or source, so baseline 3 applies.

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 verb '获取' (get), the resource '项目详细信息' (project detail), and includes the scope '及其所有任务' (and all its tasks). This distinguishes it from siblings like get_projects (which likely lists projects without details) and task-specific retrieval tools.

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 project details with all associated tasks, but does not explicitly guide when to avoid this tool or when to use alternatives like get_projects or get_all_tasks. No exclusion criteria are provided.

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