Skip to main content
Glama

Get a firm

get_firm
Idempotent

One firm from the Corridome register: its kind, location, website and SEC identifiers; the funds it reports on Form ADV, their gross assets added up by year and the funds it no longer reports, each citing its filing; its latest deals and roles; the firms it works with; its portfolio companies; what it looks for (its investment thesis: sectors, size, places, kinds of deal and the companies it holds now, each with the sentences from its own pages); what its Form ADV brochure states of its assets, fees, minimums, owners, affiliates and custodians, in the brochure's words (get_brochure has every part); which of a phone line and a mailbox its own site prints; and the people its filings and website name, with their titles and which kinds of contact are published. With include_contacts, it also returns the firm's own mailboxes and phone lines, using one credit for the firm, and those people's published business contacts, using one credit for each contact opened, from the account's monthly allowance.

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": {
      "firm_id": "<firm_id>"
    },
    "name": "get_firm"
  }
}

Input Schema

NameRequiredDescriptionDefault
firm_idYesThe firm's id from search_firms (for example ria-158763), or its corridome.com address.
include_contactsNoAlso return each person's published business contact (email, phone, LinkedIn profile). Each contact opened uses one credit from the account's monthly allowance; a person with no contact, a contact that is only a LinkedIn profile, or one already opened this month uses none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

The description goes well past the annotations by disclosing the credit model: one credit for the firm, one per contact opened, drawn from the account's monthly allowance, with free cases spelled out (no contact, LinkedIn-only, already opened this month). That billing and side-effect context is exactly the kind of behavior an agent must know before calling, and it is absent from the structured fields. It does not contradict the readOnlyHint=false annotation, since the call does consume credits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the key statement and contains no filler sentences, but the payload is delivered as one sprawling semicolon chain that is hard to scan. Given the absence of an output schema the enumeration is defensible, yet it could have been broken into a short purpose sentence plus a compact bulleted content list.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly, including the credit cost and the routing of full brochure detail to get_brochure. What is missing is only secondary: whether the record can be fetched by domain versus id is left to the schema, and error or not-found behavior is unstated. For a two-parameter read tool this is close to complete.

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, and the description still adds meaning: it clarifies that include_contacts returns not just people's published contacts but also the firm's own mailboxes and phone lines, a distinction the schema text does not make. The free-versus-charged contact cases are also restated in prose, reinforcing the schema. Marginal but real added value over the schema.

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 opening clause names the resource precisely ("One firm from the Corridome register") and then enumerates the payload: ADV identifiers, funds, deals, affiliations, portfolio companies, thesis, brochure summary, site contacts, and people. It also distinguishes itself from get_brochure by stating "get_brochure has every part," so an agent can tell the two apart. It loses a point only because the mass of return-value enumeration crowds out a crisp statement of the action.

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 implied rather than stated: the get_brochure aside signals this is the summarized view versus the full brochure, and the schema points at search_firms for the id. There is no explicit "use this when...", no when-not guidance, and no mention of alternatives like get_fund or get_affiliation for narrower needs. The reader must infer routing from the field list.

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