Skip to main content
Glama

Company details

company_get
Read-onlyIdempotent

One of your companies. Every member sees name, country, city, verification state, your role and the count of verified documents. Owners and admins also see legal name, registration numbers, contact details, address and the verification note. The version is needed as ifVersion for company_update. Free text is wrapped as data.

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": "<company>"
    },
    "name": "company_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, yet the description adds real behavioral context: output is role-shaped (members vs owners/admins see different field sets), the version field feeds optimistic concurrency in company_update, and free text is echoed as wrapped data. It stops short of describing not-found or permission-denied behavior, which matters for a single-record read.

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?

Four tight sentences, each carrying distinct information: visibility tiers, elevated fields, the ifVersion link, and the free-text wrapping note. The leading fragment is slightly awkward as an opener but nothing is redundant.

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 full burden of explaining return values and does so field by field, split by caller role, plus the version hand-off to company_update. Only error-state behavior is absent, which is a minor gap for a simple one-parameter read.

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?

There is exactly one parameter and the schema documents it fully, including the CO-XXXXXXXX pattern and its provenance (company_list_mine). The description adds no further meaning about the ref, so with 100% schema coverage the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the fragment "One of your companies" and then enumerates returned fields, so the intent (fetch details of a single company) is only implied rather than stated with a verb. It never names the input ref as the selector or contrasts itself with company_list_mine or get_company_info, leaving the agent to infer the single-vs-many distinction.

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 line "The version is needed as ifVersion for company_update" is a genuinely useful usage hook that ties this call to a sibling mutation. Beyond that there is no when-to-use guidance, no statement of when to prefer it over company_list_mine or get_company_info, and no note about what to do if the caller lacks access.

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