Skip to main content
Glama

update_project_estimate

Update a project's estimate by providing the project ID and optionally setting a new name, description, or external identifiers.

Instructions

Update the estimate for a project.

Args: project_id: UUID of the project name: New name for the estimate description: New description external_id: External system identifier external_source: External system source name

Returns: Updated Estimate object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
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
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only states 'Update' and 'Returns Updated Estimate object,' with no mention of partial-update semantics, permissions, or side effects. This is insufficient for a mutation tool with zero annotation coverage.

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?

The description is concise and well-structured with Args and Returns sections. Each line is informative, though the parameter descriptions are minimal and could be merged with schema details without losing clarity.

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?

The output schema exists, so return format is covered without description explanation. However, the description omits critical behavioral context like whether updates are partial or merge-based, error conditions, and when to prefer this tool over related estimate tools. Given 5 parameters and no annotations, it is not fully complete.

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 description lists each parameter with brief semantic labels, clarifying that project_id is a UUID and external_id/external_source relate to external systems. However, these mostly restate the schema property names and do not explain that null values may leave fields unchanged. With 0% schema description coverage, the description only partially compensates.

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 'Update the estimate for a project' with a specific verb and resource. This distinguishes it from sibling tools like create_project_estimate and delete_project_estimate, as well as update_project.

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 when-to-use guidance is provided. The description does not mention alternatives such as create_project_estimate or get_project_estimate, nor does it explain when updating an estimate is appropriate versus other project operations.

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