Skip to main content
Glama

Get several deals

get_deals
Read-onlyIdempotent

Several deals at once, up to 25: each one's company, date, type, value and every party with its role (buyer, seller, each side's advisers). Use it whenever more than one deal's parties or advisers are wanted (who advised these deals), instead of get_deal once a deal. get_deal is for one deal's full record: its text, its people and its filing.

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": {
      "deal_ids": "<deal_ids>"
    },
    "name": "get_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idsYesThe deals' ids from search_deals or get_firm (for example d1a2b3c4d5e), or their corridome.com addresses. Up to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered; the description's added value is disclosing what comes back — per-deal companies, dates, types, values, and party roles such as buyer, seller, and each side's advisers. It does not say what happens when one of the up-to-25 ids is invalid or missing, which is the main unaddressed behavior for a batch fetch.

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?

Two dense sentences, front-loaded with the batch scope before the routing advice; nothing is filler. The phrase 'instead of get_deal once a deal' is slightly compressed and reads awkwardly, but the meaning survives.

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?

There is no output schema, and the description compensates by naming the returned fields and party roles, which is exactly the missing piece for a batch fetch tool. Only the partial-failure behavior for bad ids is left uncovered.

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 100% and there is a single parameter, so the schema already documents deal_ids, its sources, format, and the 25-id cap. The description's mention of 'up to 25' restates the schema without adding format or error-handling detail, so baseline 3 applies.

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 ('Several deals at once, up to 25') and enumerates what each record carries: company, date, type, value, and every party with its role. It explicitly separates itself from the sibling get_deal, so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete selection rule: use this whenever more than one deal's parties or advisers are wanted ('who advised these deals'), and reserve get_deal for a single deal's full record including text, people, and filing. Both the when and the alternative are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources