Skip to main content
Glama

deviCERTS medical device regulatory data

Search manufacturers

search_manufacturers
Read-onlyIdempotent

Search medical device manufacturers by company name, optionally in one country, with offset paging. Returns up to 20 companies per page with slug, page URL and country, the total and next_offset. Use when a company is named or looked for. Do not use to find devices (use search_devices, which also filters by manufacturer name). Pass a slug to get_manufacturer for the company record. Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

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

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page, integer 1 to 20. Default 10.
queryYesWords of the company name, 2 to 100 characters. e.g. "philips", "B. Braun"
offsetNoNumber of results to skip, integer 0 to 999. Default 0. Pass next_offset from the previous page to get the next one; offset plus limit stays within the first 1000 results.
countryNoOnly manufacturers registered with this country in a registry (EUDAMED or FDA address): a two-letter ISO 3166-1 alpha-2 code. e.g. DE, US, NL. Default: all countries.

Output Schema

NameRequiredDescriptionDefault
totalYes
formatYes
offsetYes
cite_asYes
resultsYes
next_offsetYes
retrieved_atYes
status_as_ofYes
canonical_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Only manufacturers registered with this country in a registry (EUDAMED or FDA address): a two-letter ISO 3166-1 alpha-2 code. e.g. DE, US, NL. Default: all countries.",
      +  "pattern": "^[A-Za-z]{2}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results, 1 to 20. Default 10."New value: +"Results per page, integer 1 to 20. Default 10."
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Number of results to skip, integer 0 to 999. Default 0. Pass next_offset from the previous page to get the next one; offset plus limit stays within the first 1000 results.",
      +  "maximum": 999,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Words of the company name."New value: +"Words of the company name, 2 to 100 characters. e.g. \"philips\", \"B. Braun\""
    • addedOutput schema / properties / next_offset
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / offset
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "format",
      -  "canonical_url",
      -  "cite_as",
      -  "retrieved_at",
      -  "status_as_of",
      -  "results"
      -]New value: +[
      +  "format",
      +  "canonical_url",
      +  "cite_as",
      +  "retrieved_at",
      +  "status_as_of",
      +  "total",
      +  "offset",
      +  "next_offset",
      +  "results"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description goes well beyond them: the page size and returned fields, data provenance (EUDAMED and U.S. FDA), sync cadence, a 1-hour cache, a 300 calls/minute per-IP limit, and no login required. Those operational details materially affect how an agent should call and retry the tool.

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?

Front-loaded with purpose, then routing advice, then operational limits, with no filler or repetition of the title. It is fairly dense in the final sentence (sync cadence plus cache plus rate limit), which is useful but could be trimmed slightly.

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?

For a paginated read-only search with an output schema and annotation coverage, the description supplies scope, alternatives, chaining, provenance and rate limits. Nothing needed to select or invoke it correctly is missing.

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 limit, query, offset and country are already fully documented, including the country-as-registry-address meaning and the next_offset paging idiom. The description restates 'one country' and 'offset paging' but adds no format or edge-case detail beyond the schema, so the 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?

States a specific verb and resource ('Search medical device manufacturers by company name'), plus scope limits (single optional country, offset paging), and explicitly distinguishes itself from search_devices. An agent can pick this tool without opening any 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 an explicit when ('Use when a company is named or looked for'), an explicit when-not with the correct alternative ('Do not use to find devices - use search_devices'), and a follow-on routing step ('Pass a slug to get_manufacturer for the company record'). Both the exclusion and the handoff are spelled out.

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.