Skip to main content
Glama

create_project_estimate

Create a new estimate for a project by specifying name, type, and optional details to set up estimation in Plane CE.

Instructions

Create a new estimate for a project.

Args: project_id: UUID of the project name: Name of the estimate (e.g., "Story Points", "T-Shirt Sizes") type: Estimate type - "categories", "points", or "time" description: Optional description last_used: Whether this becomes the active estimate (default True) external_id: External system identifier external_source: External system source name

Returns: Created Estimate object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
typeNo
last_usedNo
project_idYes
descriptionNo
external_idNo
external_sourceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameYes
typeNo
projectNo
last_usedNo
workspaceNo
created_atNo
created_byNo
updated_atNo
updated_byNo
descriptionNo
external_idNo
external_sourceNo
Behavior3/5

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

Annotations indicate mutability (readOnlyHint=false) but description adds minimal behavioral context beyond what annotations provide. The default value of last_used=true is noted, but other side effects are omitted.

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?

Well-structured with Args and Returns sections, and the main purpose is front-loaded. Could be more concise by omitting redundant parameter details already in the schema.

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?

Covers basic creation but misses guidance on when to use this vs. create_project_estimate_points, and does not fully explain the 'type' parameter or external system fields. Output schema exists but is not detailed.

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 0%, so description provides essential meaning for parameters (e.g., 'UUID of the project', 'Name of the estimate...'). However, it lacks detail on the 'type' parameter values and implications of external_id/source.

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 'Create a new estimate for a project' with a specific verb and resource, distinguishing it from sibling tools like create_project_estimate_points, update_project_estimate, and delete_project_estimate.

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?

No explicit guidance on when to use this tool versus alternatives like create_project_estimate_points. The description lists parameters but does not provide context for selection.

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/Bl4nk44/plane-ce-mcp'

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