Skip to main content
Glama

Starfile

A company’s record across agencies

company_record
Read-onlyIdempotent

Everything Starfile holds on one company across agencies: FDA and CPSC recalls, clinical trials it sponsors, nursing homes it owns or runs (CMS), and aircraft registered to it (FAA), with counts, first and last dates and links. Organisations only. Says whether the match is by official id or by name.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name, e.g. "Acme Health Holdings".
limitNoMax results (default 10, max 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds genuinely new behavioral context: that counts, first/last dates and links are returned, and that the result states whether matching was by official id or by name — an important interpretation cue.

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?

Two dense sentences with no filler: the aggregate scope and source list come first, followed by the payoff details (counts, dates, links) and matching semantics. Nothing is redundant with the title.

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 explaining return content, and it does so adequately by describing counts, date ranges, links and match mode. It stops short of covering what an empty result means or how the limit interacts with the many record types, which is a minor gap.

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 both 'name' and 'limit' (default 10, max 25) are already documented with examples and bounds. The description contributes only the constraint that the name should be an organisation, which is a small but real addition; baseline 3 applies.

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?

Names a specific verb-like outcome ('everything Starfile holds on one company') plus the exact resource scope, and enumerates the constituent data sets (FDA/CPSC recalls, trials, CMS nursing homes, FAA aircraft). This lets an agent distinguish it from the narrower siblings such as aircraft_owner or search_recalls without opening their schemas.

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 description implies when to use it (an aggregate cross-agency view of one company) and adds a real constraint, 'Organisations only', which rules out person lookups. However it names no alternative and gives no explicit when-not guidance, so an agent must infer that point queries belong to the single-agency siblings.

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