Skip to main content
Glama

Get a company

get_company
Idempotent

One company from the Corridome register: its sector, the firms that own or owned it, and its deals; and for a company its public records name, what they say: staff, industry, formation date, legal form, PPP loan, retirement plans, OSHA summaries, the people named there, and which contacts the records give (contacts_on_file). With include_contacts, it also returns the company's phone and e-mail and its named people's own work lines, using one credit from the account's monthly allowance for the company.

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": {
      "company_id": "<company_id>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesThe company's id from get_deal or get_firm (for example c1a2b3c4d5e), or its corridome.com address.
include_contactsNoAlso return the company's phone and e-mail and its named people's own work lines, from its public records. Opening them uses one credit from the account's monthly allowance, the same credits a person's contact uses: one for the company, its own lines and its people's together; a company with no contact on file costs nothing, and one already opened this month is free. Use it only when the person asks for contact details, and say how many credits it used. The record says which contacts are on file either way (contacts_on_file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_contacts
      Added value: +{
      +  "default": false,
      +  "description": "Also return the company's phone and e-mail and its named people's own work lines, from its public records. Opening them uses one credit from the account's monthly allowance, the same credits a person's contact uses: one for the company, its own lines and its people's together; a company with no contact on file costs nothing, and one already opened this month is free. Use it only when the person asks for contact details, and say how many credits it used. The record says which contacts are on file either way (contacts_on_file).",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotation readOnlyHint=false might look odd for a get_ tool, but the description explains it: opening contacts consumes one credit from the account's monthly allowance, with a named free case (no contact on file) and a repeat-month free case. That is real behavioral context beyond the annotations. It does not cover error behavior or what happens with an invalid or expired id.

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 reasonably front-loaded with the resource identity and nothing is marketing filler, but the first sentence is a semicolon-chained run-on that is genuinely hard to parse on first read. Size is defensible for a two-parameter, no-output-schema tool, yet the structure could be reordered into a clean summary plus a credit note.

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, so the description carries the burden of explaining return contents, and it does so comprehensively — register facts, ownership, deals, public-record categories, named people, and the contacts_on_file indicator. Credit accounting is also disclosed. It stops short of noting how large the payload may be or how missing public records are represented.

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%, so the schema already documents both parameters in detail, including the credit mechanics and contacts_on_file. The description largely restates the include_contacts cost model and does not add syntax, id-format, or fallback guidance beyond what the schema gives. Baseline 3 is appropriate.

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 a specific verb and resource — one company from the Corridome register — and enumerates what comes back (sector, owners, deals, public-record facts, named people). An agent can distinguish it from list_companies/find_companies as a single-record detail fetch. The sentence is tangled ('for a company its public records name, what they say'), which costs it a point.

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?

The only explicit conditional guidance is parameter-level: 'Use it only when the person asks for contact details.' There is no tool-level statement of when to call get_company versus find_companies, list_companies, or search, so the agent must infer that it is the by-id detail lookup from the required company_id param.

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