Skip to main content
Glama

Proteomes Search

proteomes_search
Read-onlyIdempotent

"Reference proteome for [organism]" / "complete protein set of [species]", search UniProt reference proteomes (the curated representative protein set per organism). Use as a starting point for genome-scale protein analyses.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "homo sapiens"
    },
    "name": "proteomes_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
queryYes

Output Schema

NameRequiredDescriptionDefault
facetsNoSearch facets
resultsNoArray of proteome entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds the meaningful semantic that results are curated representative sets rather than all known proteins, but says nothing about result volume, paging, or how `size` bounds the response.

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?

Compact and front-loaded: the concept, its gloss, and the usage note arrive in three short clauses. The slash-separated quoted phrasings at the start read slightly like keyword-matching boilerplate rather than prose, which keeps it from a 5.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The remaining gap is parameter documentation on a 0%-coverage schema, which is left entirely unaddressed for `size`.

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?

Schema description coverage is 0%, so the description must carry both parameters. It implies `query` is an organism/species name via the '[organism]'/'[species]' phrasing, but `size` is never mentioned in the description or schema, leaving its units and default undocumented.

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?

States a specific verb and resource ('search UniProt reference proteomes') and glosses the concept as 'the curated representative protein set per organism', which an agent can map from phrasing like 'complete protein set of [species]'. It does not, however, differentiate itself from nearby siblings such as uniprot_search or taxonomy_search.

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?

'Use as a starting point for genome-scale protein analyses' implies a usage context, but there is no explicit when-to-use-this-vs-alternative guidance and no exclusion (e.g. when to prefer uniprot_search for individual proteins). The agent must infer selection from sibling names.

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.