Corridome

Save a search to a folder

save_search_to_folder

Idempotent

Saves a deal finder search, a people search or a name search in a folder. It keeps running there, and the folder says which matches are new since the account last looked.

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>",
      "finder": "<finder>"
    },
    "name": "save_search_to_folder"
  }
}

Input Schema

Name	Required	Description
`name`	No	people: part of the name.
`role`	No	deals: the matching firm's role.
`side`	No	deals: the matching firm's side.
`label`	No	What to call it in the folder. Left out, the search is named for its filters.
`query`	No	names: what to search for.
`state`	No	deals or people: the firm's state, two letters.
`title`	No	people: part of a title.
`finder`	Yes	deals: the deal finder's filters (as search_deals takes them). people: people search's (as search_people). names: the site's name search.
`sector`	No	deals: the company's sector.
`company`	No	deals: part of the company's name.
`firm_id`	No	deals or people: one firm, by its id from search_firms or its corridome.com address.
`year_to`	No	deals: last year.
`deal_type`	No	deals: the kind of deal.
`firm_kind`	No	deals or people: the kind of firm.
`folder_id`	Yes	The folder's id, from list_folders or get_folder.
`year_from`	No	deals: first year.
`with_contact`	No	people: only those with this kind of published contact.
`max_value_musd`	No	deals: highest disclosed value, $ millions.
`min_value_musd`	No	deals: lowest disclosed value, $ millions.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only cover the safety profile (not read-only, idempotent, non-destructive). The description adds genuinely useful behavior beyond that: the saved search keeps running inside the folder and the folder flags matches new since the account last looked, which tells the agent this is a persistent subscription rather than a one-time copy. It omits limits such as maximum items per folder or whether re-saving an identical search is a no-op.

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 short sentences with the core action first and the persistent-running behavior second. No filler, no restatement of the title.

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 19-parameter mutation with no output schema and full schema coverage, the description supplies the one thing the schema cannot: what saving actually does downstream. It stops short of explaining the return (e.g. a folder item id) or folder capacity limits, which leaves a small gap.

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 19 parameters, including the finder enum cross-referencing search_deals/search_people, are already documented in the schema. The description adds no parameter-level meaning, so the baseline of 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?

The description names a specific verb (saves) and resource (a deal finder, people, or name search) and adds the destination (a folder). The 'in a folder' framing separates it from the read-only search_deals/search_people siblings, though it never names them explicitly.

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 only implied: an agent infers you use this to persist a search rather than run one. There is no explicit when-to-use versus search_deals, add_to_folder, or create_folder, and no stated prerequisites such as needing an existing folder_id.

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

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