SiteCheck Web Intel

GTEx Portal gene expression: median TPM of one gene

search_gtex_gene_expression

Read-only

GTEx Portal gene expression (public API v2, no key): median TPM of one gene in human tissues, sorted highest first, with the GENCODE id it was matched to. Uses GTEx v8 data; unknown gene symbols return 404. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); 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": "search_gtex_gene_expression"
  }
}

Input Schema

Name	Required	Description	Default
`gene`	Yes	Gene symbol such as BRCA1 (letters, digits and dash, up to 20 characters)
`limit`	No	How many tissues, 1 to 54 (default 10)

Output Schema

Name	Required	Description	Default
`gene`	No
`unit`	No
`source`	No
`dataset`	No
`tissues`	No
`checkedAt`	No
`gencodeId`	No
`tissueCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses data version (GTEx v8), sort order, matched GENCODE id, public API v2 with no key, 404 behavior for unknown symbols, and x402 payment terms including that failed calls are not charged. These are meaningful operational facts an agent would not get from the annotations or schema.

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 description is dense and front-loaded: the purpose and return shape come first, followed by version/error behavior and payment terms. Every sentence carries useful information, though the pricing clause is the least relevant to invocation correctness and could be trimmed.

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 read-only lookup with an output schema, the description covers data source, version, sort semantics, error behavior, and payment model. Nothing an agent needs to call it correctly is 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 in the schema. The description adds only indirect meaning ('sorted highest first' hints at how the limit parameter applies) and does not add format or validation detail beyond the schema.

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 states a specific verb and resource ('GTEx Portal gene expression ... median TPM of one gene in human tissues') and names the exact output shape (median TPM, sorted highest first, GENCODE id). This clearly distinguishes it from the sibling search_* tools, which are news, ranking, and metadata sources rather than tissue expression data.

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?

The description implies when this tool is appropriate (single-gene tissue expression lookup) and notes that unknown gene symbols return 404, which is useful failure guidance. However, it does not explicitly state when not to use it or name an alternative for related tasks such as multi-gene or version-specific queries.

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

All SiteCheck Web Intel tools Inspect

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

Need Help?