Skip to main content
Glama
Sign In

Corridome

by com.corridome
OverviewDiscussionsAdmin

Move or copy items

move_folder_items

Moves or copies records and saved searches from one folder to another.

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_id": "<folder_id>",
      "item_ids": "<item_ids>",
      "to_folder_id": "<to_folder_id>"
    },
    "name": "move_folder_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomove takes them out of folder_id; copy leaves them there too (a record can sit in many folders).move
item_idsYesItem ids as get_folder returns them ("firm:ria-156472", "search:3f2a…").
folder_idYesThe folder's id, from list_folders or get_folder.
to_folder_idYesThe folder to move or copy them to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, and the description is consistent with them. It adds little beyond that: it does not say that move removes items from the source folder, that copy can leave a record in many folders, or anything about batch limits. Those facts live only in the schema's parameter descriptions.

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 no filler or repetition. It is efficient but arguably undersized for a mutating, four-parameter tool, so not a top score.

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

Completeness3/5

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

For a mutation tool the definition is thin. Annotations cover the safety profile and the schema fully covers parameters, but the description says nothing about error conditions, the 100-item cap, or what happens to items on partial failure. An agent could call it correctly but would not anticipate failures.

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 description coverage is 100%, so all four parameters are already documented, including the important move-vs-copy semantics in mode. The description's only added meaning is naming what item_ids can contain (records and saved searches), which is marginal. Baseline 3 applies.

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?

"Moves or copies records and saved searches from one folder to another" gives a specific verb pair and concrete resources (records, saved searches) plus the source/target relationship. It is clear on its own but does not distinguish itself from overlapping siblings like add_to_folder, remove_from_folder, or update_folder_item.

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?

There is no when-to-use or when-not-to-use guidance. With add_to_folder, remove_from_folder, and update_folder_item in the sibling set, an agent is left to infer that this tool is for relocating existing items between folders rather than linking or editing them. Move-vs-copy selection is left entirely to the schema's mode field.

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

All Corridome toolsInspect
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