amr-mcp

get_protein_hosts

Read-only

Identify species in which NCBI has sequenced an exact protein accession, returning host record counts with optional top-N limiting.

Instructions

Species in which NCBI has sequenced this exact protein (Identical Protein Groups), with record counts.

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

Input Schema

Name	Required	Description	Default
`top`	No
`accession`	Yes	Protein accession, ideally the catalog's RefSeq WP_ one, e.g. WP_004199234.1

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already establish read-only and open-world access. The description adds data provenance (NCBI Identical Protein Groups) and that counts are returned, but it omits rate limits, pagination behavior, or how 'top' limits results.

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?

A single front-loaded sentence; every phrase contributes, and there is no redundant restatement.

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

Completeness3/5

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

The tool is simple, read-only, has an output schema, and annotations cover safety; however, the description omits usage guidance and the meaning of the 'top' parameter, leaving clear gaps for correct invocation.

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

Parameters2/5

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

The schema documents accession well but leaves 'top' undocumented at 50% schema description coverage. The description does not explain that 'top' limits the number of host records or mention its default/maximum, so it fails to compensate for the schema 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?

The description names the exact output resource—species where NCBI has sequenced the exact protein via Identical Protein Groups—and mentions record counts, making it distinct from sibling search/fetch tools.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance or alternatives are named; the agent must infer from the purpose that this is for retrieving host species for a protein accession.

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

Deploy Server