Skip to main content
Glama
Sign In

Corridome

by com.corridome
OverviewDiscussionsAdmin

Add records to a folder

add_to_folder
Idempotent

Puts firms, funds, companies, deals or people in a folder, by their ids or corridome.com addresses. A record can sit in many folders.

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>",
      "records": "<records>"
    },
    "name": "add_to_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYesFirms, funds, companies, deals or people: each its id from another tool (ria-158763, f1a2b3c4d5e, c1a2b3c4d5e, d1a2b3c4d5e, p:…) or its corridome.com address.
folder_idYesThe folder's id, from list_folders or get_folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / note
      Removed value: -{
-  "description": "A note on each record added.",
-  "maxLength": 2000,
-  "type": "string"
-}
    • removedInput schema / properties / status
      Removed value: -{
-  "description": "A status for each, one of the folder's status steps.",
-  "maxLength": 40,
-  "type": "string"
-}
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent operation. The description adds meaningful behavior beyond that: records can be identified by ids or corridome.com addresses, and a record can belong to multiple folders.

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?

The description is two short sentences with no wasted wording. The core action and record types are front-loaded, followed by a useful behavioral nuance.

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?

Given the simple two-parameter operation, full schema coverage, and annotations covering safety and idempotency, the description is largely complete. It could be slightly stronger by clarifying when to choose this over move_folder_items or save_search_to_folder, but it covers the essential context for calling the tool.

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 both the records and folder_id parameters are fully documented in the input schema. The description's mention of ids and addresses mirrors the schema's records description and does not add syntax or format details beyond what is already provided.

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?

The description states a specific verb and resource: 'Puts firms, funds, companies, deals or people in a folder'. This clearly distinguishes it from siblings such as remove_from_folder and create_folder, though it does not explicitly name those alternatives.

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 explicit guidance on when to use this tool versus alternatives like move_folder_items, save_search_to_folder, or create_folder. The note that 'A record can sit in many folders' is useful behavioral context but not usage guidance.

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