Skip to main content
Glama

Get Company Details

get_company_info
Read-only

Returns the active company's full profile — basic info (name, state, entity type, EIN, industry, dashboard status, formation filing date), member list, responsible party, addresses, name options, and provisioned services. Mirrors what the customer sees on /web's Company Information page (https://app.doola.com/company). Use when the customer asks 'tell me about my company', 'what's my EIN?', 'who are the members?', or similar — distinct from get_company_onboarding_status which returns derived next-step routing rather than raw company data. It reads the active company, which switch_active_company changes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_company_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Output Schema

NameRequiredDescriptionDefault
EINNoEIN if assigned
nameNoCompany name (primary selection)
errorNotrue if an error occurred
stateNoFormation state (e.g. WY)
membersNoLLC members with ownership percentages.
messageNoError message if error=true
industryNoNAICS industry name set on the company
companyIdNoActive companyId
entityTypeNoEntity type (e.g. LLC, CCorp)
conversation_idNoThis conversation's handle. Pass it unchanged as conversation_id on every later call.
dashboardStatusNoFormation dashboard status string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "This conversation's handle. Pass it unchanged as conversation_id on every later call.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them: it discloses the dependency on the active company and points at `switch_active_company`, which explains why results can change between calls. It does not discuss payload size or whether member data is redacted, which is the only remaining gap.

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?

Front-loads the returned data, then the use cases, then the disambiguation against a sibling and the active-company dependency. Every sentence carries distinct information — field inventory, trigger phrases, sibling exclusion, state mutation note — with no filler.

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?

An output schema exists, so the description need not explain return values, and annotations cover the read-only safety profile. The remaining minor gap is that it does not say whether a company must exist or what happens if none is active, though the pointer to `switch_active_company` hints at that model.

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?

All three parameters are optional analytics fields whose schema descriptions are already fully covered at 100%, so schema does the heavy lifting. The description correctly implies the tool takes no substantive input, which is the key semantic fact an agent needs. It could explicitly say the parameters are optional and do not affect results, but the coverage baseline is already met.

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 (returns the active company's full profile) and enumerates exactly the fields returned — name, state, entity type, EIN, industry, dashboard status, formation filing date, members, responsible party, addresses, name options, provisioned services. It explicitly distinguishes itself from `get_company_onboarding_status`, so an agent can select between the two 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 concrete trigger utterances ('tell me about my company', 'what's my EIN?', 'who are the members?') plus an explicit exclusion naming the sibling to use instead for derived next-step routing. It also notes the tool reads the active company, which `switch_active_company` changes — an implicit prerequisite the agent would otherwise miss.

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.