Skip to main content
Glama
Sign In

Oliver's mTOR Atlas

by io.github.open-mtor-atlas
OverviewDiscussionsAdmin

Get one study

get_study
Read-onlyIdempotent

Full record for one study by Atlas ID (e.g. "SAB1994"), PMID, DOI or PMCID: abstract excerpt, extracted findings, linked entities, the relations it supports or contradicts, related open questions.

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_study"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias of sid.
doiNoAlias of sid, for a DOI.
sidNoAtlas study ID ("SAB1994"), PMID ("23716719"), DOI or PMCID
pmidNoAlias of sid, for a PMID.
pmcidNoAlias of sid, for a PMCID.
study_idNoAlias of sid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / doi
      Added value: +{
+  "description": "Alias of sid, for a DOI.",
+  "type": "string"
+}
    • addedInput schema / properties / pmcid
      Added value: +{
+  "description": "Alias of sid, for a PMCID.",
+  "type": "string"
+}
    • addedInput schema / properties / pmid
      Added value: +{
+  "description": "Alias of sid, for a PMID.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / sid / description
      Previous value: -"Atlas study ID, e.g. \"SAB1994\""New value: +"Atlas study ID (\"SAB1994\"), PMID (\"23716719\"), DOI or PMCID"
  3. Changed3 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Alias of sid.",
+  "type": "string"
+}
    • addedInput schema / properties / study_id
      Added value: +{
+  "description": "Alias of sid.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "sid"
-]
  4. 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/idempotentHint/non-destructive, so safety is covered; the description earns extra credit by enumerating the payload (abstract excerpt, findings, linked entities, supporting/contradicting relations, open questions), which tells an agent whether one call suffices or follow-ups are needed. It doesn't say whether the record can be truncated or what a missing ID yields.

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?

A single front-loaded sentence with a colon-delimited payload list; no filler, no repetition of the title, and the identifier forms come before the return contents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only single-record lookup with no output schema, naming the returned sections is the right amount of context, and aliasing is fully handled by the schema. Slightly short of complete because it doesn't mention behavior on unknown IDs or the size/shape of nested entity lists.

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% and every parameter is documented as an alias of sid. The description mirrors the same identifier list (Atlas ID, PMID, DOI, PMCID) rather than adding new meaning, so baseline 3 applies — though it usefully signals that only one identifier need be supplied.

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?

Specific verb + resource ('Full record for one study') with the accepted identifier forms spelled out. It is distinguishable from get_entity/get_author by resource, but never contrasts itself with search_studies, the obvious sibling for finding studies.

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 is only implied: you call it when you already have an identifier for one study. There is no explicit 'when to use this instead of search_studies' or statement about what happens if no identifier matches.

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 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