Skip to main content
Glama

create_project_estimate

Create a new estimate for a project by specifying its name, type (categories, points, or time), and optional description. Set it as the active estimate or track external identifiers.

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?

No annotations are provided, so the description carries the transparency burden. It discloses that last_used defaults to True and affects whether the estimate becomes active, and it states the return type. However, it does not mention side effects on existing estimates, permission requirements, or error conditions.

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 uses a clear Args/Returns structure with one parameter per line, including contextual examples. It is concise—no filler sentences—and every line adds value by explaining a parameter or the return value.

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

Completeness4/5

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

All parameters and the return value are covered, and the output schema handles return details. The description lacks domain context about what an 'estimate' is in this system and the implications of setting last_used, but it is otherwise complete for a create operation with a well-defined schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the Args block explains all 7 parameters with examples, type values, and defaults. For instance, type is described as 'categories', 'points', or 'time', and name includes examples like 'Story Points'. This fully compensates for the lack of schema descriptions.

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 starts with 'Create a new estimate for a project,' which is a specific verb+resource combination. It clearly distinguishes this from sibling tools like update_project_estimate, get_project_estimate, and delete_project_estimate by focusing on creation.

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 usage is implied by the verb 'Create' and the resource 'estimate.' No explicit alternatives or exclusions are provided, such as when to use link_estimate_to_project instead. It's clear but lacks guidance on choosing between related tools.

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/leigangzhang/plane-mcp-server-adapter'

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