Skip to main content
Glama

MedaRep

Device company profile

company_profile
Read-onlyIdempotent

A device company by name or slug: FDA 510(k), De Novo and PMA decisions by family and year, recalls (open first, by class), adverse-event trend against each family's category over two closed years, and consolidated financials for public parents. Needs the product and company coverage add-on; without it the answer is a notice.

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany name ("Stryker") or slug from search (stryker).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-open-world behavior, so the safety profile is covered. The description adds substantive behavior beyond that: the add-on entitlement gate with its degraded 'notice' response, recall ordering (open first, by class), and the fixed two-closed-year window for adverse-event trends.

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?

One front-loaded sentence beginning with the resource, followed by the gating condition — nothing is redundant. It is dense to the point of being a run-on list, but every clause carries distinct information about what data comes back.

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 takes on the job of describing returns and does so by enumerating the five data sections. For a one-parameter read-only tool with full schema coverage and complete safety annotations, the remaining gaps (exact response shape, entity resolution failures) are minor.

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 a single required parameter with 100% schema description coverage that already explains the name-or-slug format with examples. The description restates 'by name or slug' without adding resolution rules, disambiguation behavior, or what happens on a name mismatch, so it stays at the schema-backed baseline.

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 description names a specific resource (a device company profile) and enumerates its contents precisely: FDA 510(k), De Novo and PMA decisions by family and year, recalls, adverse-event trends, and financials for public parents. That detail distinguishes it from the sibling *_profile tools (facility, practice, surgeon), though the retrieval verb itself is only implied by the noun phrase.

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?

It states a concrete usage condition — the product and company coverage add-on is required, otherwise the answer is only a notice — which is genuinely useful. It does not, however, say when to pick this over facility_profile or practice_profile for a given entity, leaving that inference to the agent.

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