Funkel AI

rename_list

Destructive

Rename one unarchived list in the selected product after explicit approval. Supply its current name to reject stale changes; include the full new description. Over MCP: call this tool once, without confirmation_token. It runs right away and returns the result.

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": {
      "list_id": "<list_id>",
      "expected_name": "<expected_name>",
      "name": "<name>",
      "description": "<description>"
    },
    "name": "rename_list"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	New name (1-100 chars)
`list_id`	Yes	List id (UUID format, e.g. 550e8400-e29b-41d4-a716-446655440000)
`description`	Yes	New full description
`expected_name`	Yes	Current list name
`confirmation_token`	No	Approval token; omit on first call

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. The description adds what the annotations cannot: that expected_name exists to 'reject stale changes' (optimistic-concurrency protection), that approval is required, and that the call executes immediately and returns a result.

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?

Three tight sentences, front-loaded with the action and its constraints. The trailing 'and returns the result' is mild filler, but overall there is little waste.

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 destructive mutation with no output schema, the description covers the approval flow, concurrency guard, and MCP invocation semantics an agent needs. Return-value shape is not required since no output schema exists, leaving only minor gaps.

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 coverage is 100%, so the baseline is 3. The description earns above that by explaining why expected_name is supplied ('to reject stale changes') and clarifying the confirmation_token omission over MCP, information the schema labels alone do not convey.

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 with scope: 'Rename one unarchived list in the selected product.' The single-list, unarchived constraint plus the rename action clearly distinguishes it from siblings like create_list, get_list, and list_lists.

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?

Gives explicit operating context: rename only 'after explicit approval' and, over MCP, 'call this tool once, without confirmation_token.' This tells the agent how the approval gate is bypassed in MCP and that no second confirming call is needed. It stops short of naming any alternative tool, but no rename alternative exists among the siblings.

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

All Funkel AI 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?