Skip to main content
Glama

UniProt reviewed human protein entries for a gene symbol

health_uniprot_protein_knowledge
Read-only

UniProt reviewed (Swiss-Prot) human protein entries for a gene symbol: accession, protein name, gene, sequence length and the curated function summary. Human only (taxon 9606). Up to 5 entries per call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "gene": "<gene>"
    },
    "name": "health_uniprot_protein_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many entries, 1 to 5 (default 1)
geneYesHuman gene symbol, letters, digits and hyphens, 2 to 20 characters

Output Schema

NameRequiredDescriptionDefault
geneNo
sourceNo
entriesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description goes further by disclosing scope limitations (human only, max 5 entries) and, unusually, the commercial behavior: $0.002 per successful call via x402 across several networks, with failed calls not charged. That payment/rate information is genuinely useful context an agent would not get from structured fields.

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?

The core purpose and scope are front-loaded in the first clause, and the pricing sentence is clearly separated. Wording is dense but every sentence carries information; only minor tightening would be possible.

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 two-parameter lookup with an output schema, an existing annotations profile, and full schema coverage, the description supplies everything needed: what is returned, the taxonomic restriction, the result cap, and the payment requirement. Nothing an agent needs to decide or call correctly appears 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 description coverage is 100%, so both parameters are already documented, including the 'default 1' for max and the gene symbol format. The description's 'Up to 5 entries per call' reinforces max but adds nothing new about gene syntax or edge cases, which fits the baseline 3 when the schema does the heavy lifting.

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: 'UniProt reviewed (Swiss-Prot) human protein entries for a gene symbol', and even enumerates the returned fields (accession, protein name, gene, sequence length, function summary). It does not explicitly contrast with the nearest sibling, health_string_protein_networks, so the sibling-differentiation bar for a 5 isn't quite met.

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 context is implied by the constraints: human-only (taxon 9606) and a cap of 5 entries per call tell the agent the scope and when it will be truncated. There is no explicit when-to-use/when-not-to-use statement or named alternative, so it stays at the minimum-viable level.

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