Skip to main content
Glama

Update code tree

code_update
Destructive

Change a tree's title or description.

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": {
      "tree": "<tree>",
      "org": "<org>"
    },
    "name": "code_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
treeYesThe tree's name.
titleNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, which is a notable safety profile for what reads as a metadata edit; the description does not explain what is destructive, whether the change is reversible, or whether permissions are required. It also does not disclose null semantics for the nullable title/description parameters (likely clearing the field), leaving a mutation behavior unexplained.

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?

A single front-loaded sentence with zero filler. Efficiency is high, though the brevity borders on under-specification rather than true conciseness.

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

Completeness2/5

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

For a destructive mutation with half its parameters undocumented and no output schema, the description should say more: what happens on null, what the destructive aspect entails, and what the response is. As written, an agent would have to guess at the write semantics.

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 50%: org and tree are documented, while title and description have no schema descriptions. The description names those two fields as the ones being changed, partially compensating, but adds no detail on null/clearing behavior or the 500-character limit beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Change') and the exact mutable fields of the resource ('a tree's title or description'), which implicitly distinguishes it from content-mutating siblings like code_edit or code_write. No sibling is named explicitly, and 'tree' vs the sibling 'code_tree' relationship is only inferable, so it stops short of 5.

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 guidance on when to choose this over alternatives such as code_move, code_remove, or code_edit, and no preconditions for the update. The agent must infer usage entirely from the verb and field names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources