amr-mcp

get_amr_gene

Read-only

Retrieve full catalog records for a specific antimicrobial resistance allele or summarize all alleles in a gene family using an exact allele or family name.

Instructions

Full catalog record for an allele, or a summary of all alleles in a gene family.

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": "get_amr_gene"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Exact allele (e.g. 'blaKPC-2') or gene family (e.g. 'blaKPC')

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world scope are covered structurally. The description contributes the dual-mode behavior (full record for an allele, summary for a family), which is genuine added context, but it says nothing about catalog coverage, ambiguity handling, or what happens for unknown names.

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 front-loaded sentence with no filler, and the two behaviors are presented together in one clause. It is efficient, though the compressed phrasing makes the allele-versus-family distinction slightly less immediately obvious than it could be.

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 an output schema present and annotations covering the read-only, open-world profile, the description only needs to explain the two calling modes, which it does. The remaining gap is sibling routing against search_amr_genes, which is not addressed.

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% and the name parameter already documents both accepted forms with examples ('blaKPC-2' vs 'blaKPC'). The description mirrors that distinction and ties each form to a different output shape, but adds no new syntax, casing, or matching-rule detail beyond the schema.

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 verb-and-resource pair ('Full catalog record for an allele') and adds the second mode ('summary of all alleles in a gene family'), which is meaningfully more precise than the tool name alone. It does not explicitly contrast itself with the sibling search_amr_genes, so the boundary between lookup and search is left implicit.

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?

Usage is only implied: the description suggests passing an exact allele versus a gene family yields different results, but it never states when to prefer this tool over search_amr_genes or what to do when the name is unknown. An agent can infer the lookup use case but gets no exclusions or fallback guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server