Frostbyte

update_area

DestructiveIdempotent

Change an existing area's name, description or colour. Get the areaId from list_areas first. Only the fields you pass change; omitted fields keep their current values. Rename only when the user asks, since teammates know the area by its name. Tasks stay in the area, so a rename shows on all of them; to move tasks between areas use update_task, and to remove an area use delete_area. The change appears live and in the activity feed. Returns the area's resulting colour.

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": {
      "projectId": "<projectId>",
      "areaId": "<areaId>",
      "context": "<context>"
    },
    "name": "update_area"
  }
}

Input Schema

Name	Required	Description
`name`	No	New name — a word or two. Max 30 characters. Omit to keep the current name.
`color`	No	Set only when the user asks for a colour: pick the closest of #6366f1, #f97316, #22c55e, #ec4899, #06b6d4, #f59e0b, #8b5cf6, #14b8a6, #f43f5e, #3b82f6, avoiding one another area already uses (list_areas shows them), unless they give an exact 6-digit hex.
`areaId`	Yes	The area ID, from list_areas
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`projectId`	Yes	The project ID
`description`	No	New description — 1–2 short sentences on what this area groups. An empty string clears it; omit to keep it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 3, 2026

changedInput schema / properties / areaId / description

Previous value: -"The area ID"New value: +"The area ID, from list_areas"

changedInput schema / properties / description / description

Previous value: -"New description — 1–2 short sentences on what this area groups."New value: +"New description — 1–2 short sentences on what this area groups. An empty string clears it; omit to keep it."

changedInput schema / properties / name / description

Previous value: -"New name — a word or two. Max 30 characters."New value: +"New name — a word or two. Max 30 characters. Omit to keep the current name."

First observedNov 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description nonetheless adds real behavior: omitted fields are preserved, renames propagate to all tasks in the area, and the change surfaces live and in the activity feed. What it does not clarify is what 'destructive' could mean here beyond an implicit risk of renaming/clearing the description, and there is no statement about permissions or failure modes.

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?

Five short sentences, front-loaded with purpose and the prerequisite before the cautionary and cross-reference detail. Every sentence carries information; only the 'appears live and in the activity feed' clause sits near the edge of what an agent needs to call the tool correctly.

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?

For a 6-parameter mutation tool with no output schema, the description covers purpose, prerequisite, patch semantics, side effects on related tasks, sibling routing, and the returned field. Nothing an agent needs in order to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: patch semantics ('Only the fields you pass change; omitted fields keep their current values') across all optional fields, and the behavioral consequence of changing name. It also states the return value ('the area's resulting colour'), which no schema covers.

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?

States a specific verb and resource ('Change an existing area's name, description or colour') and immediately scopes it against siblings by naming update_task for moves and delete_area for removal. An agent can distinguish this from create_area, delete_area and update_task without opening any schema.

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?

Gives an explicit prerequisite ('Get the areaId from list_areas first'), an explicit conditional caution ('Rename only when the user asks, since teammates know the area by its name'), and names the two alternative tools with the conditions that select them. When-to-use, when-not-to-rename, and alternatives are all covered.

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

All Frostbyte tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?