amr-mcp

get_uniprot_entry

Read-only

Retrieve a UniProtKB entry by accession to get its function, keywords, cross-references, and protein sequence for annotation and antimicrobial resistance research.

Instructions

Function, keywords, cross-references and sequence of a UniProtKB entry.

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

Input Schema

Name	Required	Description	Default
`accession`	Yes	UniProt accession, e.g. Q9F663

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and external-API nature are covered structurally. The description adds nothing beyond them — no note on rate limits, latency of the external UniProt call, or what happens on an invalid/missing accession. Listing returned fields earns no credit because an output schema exists.

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 short phrase with zero waste, and the resource being fetched is front-loaded. It is a fragment rather than a sentence, but it is not padded and gets to the point immediately.

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?

For a one-parameter read-only lookup with a full input schema and an output schema, the essential information is present. What is missing is the routing context against the sibling search_uniprot and the failure mode for a bad accession, which leaves the definition adequate but not complete.

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?

With one parameter at 100% schema description coverage (including an example accession, Q9F663), the schema already does all the work. The description contributes no additional meaning about the accession format or species-qualified identifiers, so the baseline 3 applies.

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?

Names the specific resource ('a UniProtKB entry') and enumerates the content returned: function, keywords, cross-references and sequence. That is clearly a single-record lookup, but there is no verb and no explicit contrast with the sibling search_uniprot, so an agent must infer that this is the by-accession retrieval versus the search tool.

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 when-to-use guidance at all: nothing says to use this when you already have an accession and to use search_uniprot when you only have a name or keyword. No prerequisites, no error behavior for an unresolvable accession. The only hint is the schema's required 'accession' field.

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

Deploy Server