Skip to main content
Glama

Company file

company_file
Read-onlyIdempotent

The public record on ONE company, by the entity_id find_company returned (or a Swiss UID): identity, dated register changes, sanctions-list checks and the sections the summary lists. Without layer the answer is a summary of at most 6,000 characters; with layer (register, history, sanctions, identity, leadership, regulator, or another section the summary lists) one section, paged with cursor. as_of (YYYY-MM-DD) gives the file as it stood on a date; since (YYYY-MM-DD) lists the changes after a date, and by default the summary shows what changed since this account last opened the file. A thin file (an entity_id starting 'lei:', a company with no Swiss UID) has no history: its GLEIF record, its parents and the Swiss companies it owns, and sanctions-list checks.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "company_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
layerNo
sinceNo
cursorNo
entity_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial behavior beyond them: a 6,000-character cap on the default summary, single-section paging via `cursor`, the default `since` baselining on when this account last opened the file, and the degraded 'thin file' shape for `lei:` entities with no Swiss UID. These are exactly the runtime traits an agent cannot infer from annotations.

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?

A single dense paragraph, front-loaded with the resource and its identifier, then modes in a sensible order. Every clause carries information, though the lengthy thin-file sentence packing GLEIF record, parents, owned Swiss companies, and sanctions into one breath would read better separated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so no return-value description is required, and the description instead covers the things the schema cannot: size caps, historical semantics, pagination, defaults, and the degenerate entity case. For a 5-parameter read tool with rich annotations, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% – the schema only supplies titles and empty-string defaults – so the description carries the full burden, and it does: `layer` values are enumerated with an escape hatch to other summary-listed sections, `as_of` and `since` are given a YYYY-MM-DD format, `cursor` is tied to section paging, and `entity_id` is sourced. Only `cursor`'s opacity (no mention of page size or termination) is a small residual gap.

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 exactly what is returned: 'the public record on ONE company', enumerated into identity, dated register changes, sanctions checks, and summary-listed sections. It also pins the identifier to a specific upstream source (`entity_id` from find_company) or a Swiss UID, which cleanly separates it from the finder sibling.

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

Usage Guidelines4/5

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

Gives concrete selection guidance for each mode: omit `layer` for a summary, supply `layer` for a single section, use `as_of` for point-in-time, `since` for a change list, `cursor` for paging. It routes the agent to find_company for the id but never states an explicit exclusion or what to do when the entity is unknown or ambiguous.

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.