Skip to main content
Glama
evalor
by evalor

Get Project

get_project

Retrieve project metadata by ID to verify existence and check settings. Returns name, color, viewMode, and permissions without tasks.

Instructions

Retrieve metadata for a single project (清单) by ID.

WHEN TO USE:

  • Check project settings (name/名称, color/颜色, viewMode/视图模式, permissions)

  • Verify a project exists before operations

  • Get project metadata without loading tasks

WHEN NOT TO USE:

  • Need tasks within the project (清单内的任务) → use 'get_project_data' or 'list_tasks'

  • Need to filter tasks by date/priority (按日期/优先级筛选) → use 'list_tasks'

RETURNS: Project metadata only (id, name/名称, color/颜色, viewMode/视图模式, kind/类型, permissions). Does NOT include tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe unique ID of the project to retrieve (清单ID)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
kindNo
nameYes
colorNo
closedNo
groupIdNo
viewModeNo
sortOrderNo
permissionNo
Behavior5/5

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

No annotations provided, so description fully covers behavior. Clearly states return value (project metadata only) and what it excludes (tasks). Implies read-only operation.

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?

Well-structured with clear sections. Every sentence adds value, no redundancy. Concise yet informative.

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

Completeness5/5

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

Given the simple single-parameter tool and existence of an output schema, the description is complete. It specifies what is returned and what is not, aligning with typical usage.

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% with description for projectId explaining it's the unique ID. Description adds context 'by ID' but does not add significant value beyond schema. Baseline 3.

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 states 'Retrieve metadata for a single project by ID', providing a specific verb and resource. It distinguishes from siblings like get_project_data and list_tasks by clarifying scope.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE and WHEN NOT TO USE sections with clear alternatives (get_project_data, list_tasks). Provides precise guidance on when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/evalor/Dida365MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server