Hook Detector

rename_folder

Rename a folder, change its description, or both. A name another folder on the tab already has is 409 folder_exists. Returns the folder. Same as PATCH /v1/folders/{folder_id}. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rename_folder"
  }
}

Input Schema

Name	Required	Description
`name`	No	a new name, 1 to 80 characters
`api_key`	No
`folder_id`	No	one of your folders (from list_folders or create_folder)
`description`	No	a new description; "" clears it, left out it stays

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations to lean on, the description does real work: it discloses the duplicate-name failure (409 folder_exists), states that the folder is returned, maps to PATCH /v1/folders/{folder_id}, and notes the call is free. It stops short of covering auth/permission requirements for mutating a folder.

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?

Four short sentences, front-loaded with the primary action, then the failure mode, return value, API mapping, and cost. Nothing is padded and each sentence carries distinct information.

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 mutation tool with no annotations but an output schema, the definition covers the key failure mode, return behavior, and semantics of partial updates. Only auth/permission context and an explicit contrast with other folder-mutation siblings are missing.

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 75% and the schema already documents the name length bound and that an empty description clears it while an omitted one persists. The description's 'or both' adds the useful point that name and description can be changed together, but otherwise defers to the schema.

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 and resource ('Rename a folder') plus the secondary operation ('change its description, or both'), so the agent knows exactly what mutation happens. It doesn't explicitly contrast with sibling edit_folder_item or save_to_folder, so sibling differentiation is only implied.

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?

Usage is implied by the description of what it does, and the 409 folder_exists condition signals a real constraint, but there is no explicit 'use this instead of X' guidance and no prerequisites (e.g., ownership or key requirements) are stated.

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

All Hook Detector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?