Oliver's mTOR Atlas

Get one entity

get_entity

Read-onlyIdempotent

One entity (gene/protein, complex, drug, disease, process...) with its linked studies as short cards (first studies_limit) and every pathway relation it takes part in as a one-line claim. Accepts an id, a name or a synonym.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_entity"
  }
}

Input Schema

Name	Required	Description
`id`	No	Alias of entity.
`entity`	No	e.g. "mTORC1", "Rheb", "rapamycin"
`studies_limit`	No	Maximum 50; a larger value is capped at 50.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 13, 2026

addedInput schema / properties / id

Added value: +{
+  "description": "Alias of entity.",
+  "type": "string"
+}

addedInput schema / properties / studies_limit / description

Added value: +"Maximum 50; a larger value is capped at 50."

changedInput schema / properties / studies_limit / maximum
```
Previous value: -50New value: +9007199254740991
```
removedInput schema / required
```
Removed value: -[
-  "entity"
-]
```

First observedOct 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds the shape of the payload (linked studies as short cards, pathway relations as one-line claims) and the studies_limit truncation, but says nothing about ambiguity or error behavior when a name matches multiple entities.

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?

Two sentences, front-loaded with the resource and its scope, with the accepted-key note placed last. Dense but every clause carries information; no filler.

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?

With no output schema, the description does the necessary work of describing the returned payload, which is its main strength. It leaves open what happens with zero arguments (nothing is required) and how ambiguous names are resolved, gaps an agent would hit in practice.

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 all three parameters are documented in the schema (including the 50-study cap). The description adds only the clarification that id/name/synonym are interchangeable lookup keys, which is modest value over the schema's own 'Alias of entity' note.

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+resource ('One entity') and enumerates the entity types it covers (gene/protein, complex, drug, disease, process), which clearly separates it from the plural search_entities. It stops short of explicitly naming the sibling it is the singular counterpart of, so an agent must infer the split.

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 clause 'Accepts an id, a name or a synonym' implies you call this when you already have a concrete identifier, versus using search_entities to discover one. There is no explicit when-to-use/when-not statement and no guidance on which of the two identifiers to prefer.

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

All Oliver's mTOR Atlas 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.