Skip to main content
Glama
Sign In

Protein Atlas

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Protein

get_protein
Read-onlyIdempotent

Get a trimmed Human Protein Atlas profile for one protein by Ensembl gene id (e.g. "ENSG00000146648"): gene, description, protein class, biological process, molecular function, RNA tissue specificity/distribution, subcellular location, and disease involvement. Use search_genes to find the Ensembl id. Keyless.

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": {
      "ensembl_id": "ENSG00000146648"
    },
    "name": "get_protein"
  }
}

Input Schema

NameRequiredDescriptionDefault
ensembl_idYesAn Ensembl gene id like "ENSG00000146648".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ensembl_id": "ENSG00000146648"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, conveying that the tool is safe and idempotent. The description adds behavioral context by stating the tool returns a 'trimmed' profile (implying a subset of data), listing the specific fields, and noting 'Keyless' (likely meaning no authentication required). This adds value beyond the annotations.

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?

The description is extremely concise: two sentences that front-load the purpose with the verb 'Get'. It wastes no words and includes a code example and a usage hint. Every sentence earns its place.

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?

Given the tool's simplicity (one parameter, no output schema), the description is complete. It enumerates the return fields and mentions keyless access. There are no obvious gaps for a user to understand input, output, and behavior.

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% for the single parameter 'ensembl_id', so the schema already documents it fully. The description adds an example ID ('ENSG00000146648') which helps illustrate the format, but does not provide additional semantic meaning. According to guidelines, baseline is 3 when coverage is high, and the example is a minor improvement.

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 clearly states the action ('Get') and the resource ('trimmed Human Protein Atlas profile for one protein by Ensembl gene id'). It lists the specific data fields returned and provides an example Ensembl ID, making the tool's purpose unmistakable. It also distinguishes itself from the sibling tool 'search_genes' by directing users to use that tool to find the Ensembl ID.

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

Usage Guidelines4/5

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

The description explicitly mentions using 'search_genes' to find the Ensembl ID, providing a clear alternative for discovery. However, it does not specify when not to use this tool or other potential alternatives beyond that. For a simple lookup tool, this level of guidance is sufficient but not exhaustive.

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

All Protein Atlas toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources