Skip to main content
Glama

Update folder

update_folder
Idempotent

Rename a note folder, move it into another (or to the top), pin it to the top of the folder list, or give it an emoji. Folders are created by capture or update_note's folder argument.

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": {
      "folder": "<folder>"
    },
    "name": "update_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoAn emoji, or "" for none.
nameNoA new name.
folderYesThe folder's path, e.g. "Projects/Alpha".
parentNoA folder path to move it into, or "/" for the top.
pinnedNoPin it to the top of the folder list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover mutability, idempotency and scope, so the bar is lower; the description adds the meaningful behavioral fact that folders cannot be created here, closing a real failure mode. It does not say what happens when the target folder or parent path does not exist, which would be the remaining gap.

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?

Two sentences, operations front-loaded, no wasted words. The creation note is placed exactly where it prevents a wrong invocation.

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?

For a 5-parameter mutation tool with full schema coverage and annotations, this is nearly complete: capabilities and creation boundary are both covered. Only failure semantics for a missing folder path are unaddressed.

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 100% and every parameter already carries a description, including the '/' convention for the top level and the emoji/empty-string case. The description merely restates the same four capabilities in prose, adding no format or edge-case meaning beyond the schema.

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 (rename/move/pin/set emoji) on a specific resource (note folder) and enumerates the exact operations the tool supports. The second sentence about folder creation differentiates it from capture and update_note, so an agent knows this tool does not create folders.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'Folders are created by capture or update_note's folder argument' effectively tells the agent when NOT to reach for this tool and where creation lives instead. It stops short of explicit guidance such as using list_folders to resolve a path before calling, but the usage context is clear.

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