Skip to main content
Glama
Sign In
Oliver's mTOR Atlas

Oliver's mTOR Atlas

by open-mtor-atlas
OverviewSchemaSourceRelated ServersDiscussionsAdmin

Find pathway relations

find_relations
Read-onlyIdempotent

Find signed, evidence-linked mTOR pathway relations and filter them by entity, source, target, effect, contested status or minimum evidence strength.

Instructions

Signed, evidence-linked pathway relations (claims such as "Rheb activates mTORC1"). Filter by an entity on either end, by source/target, effect, contested status or minimum strength of the best supporting evidence.

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": "find_relations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
effectNo
entityNoEntity on either end of the relation
offsetNoFor the next page: pass next_offset from the previous answer.
sourceNo
targetNo
contested_onlyNoOnly relations marked contested or with conflicting studies
strongest_at_leastNoKeep relations whose best supporting study is at least this code in the order S > H > A > M

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds domain-meaningful context ('signed, evidence-linked', filterable by contested status), but says nothing about result volume, pagination behavior, or what an empty result means.

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, no filler, with the nature of the resource front-loaded before the filtering options. The parenthetical example earns its place by disambiguating 'signed relation'.

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?

For an 8-parameter, zero-required search tool with no output schema, the description covers filtering but not result shape or paging (offset/next_offset only appear in the schema). It also gives no help decoding the strength codes, which are ambiguous in the schema itself (enum includes R/PP/RT while the ordering note stops at M).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, so the description must compensate, and it does: entity, source/target, effect, contested status, and strength threshold are all named in prose. It omits limit/offset semantics, but offset is documented in the schema itself.

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 concrete verb and resource ('Find pathway relations') and clarifies what a relation actually is with an example ('Rheb activates mTORC1'), plus the qualifier 'signed, evidence-linked'. This clearly separates it from a single-record lookup like get_relation, though no sibling is named explicitly.

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 second sentence enumerates the available filter dimensions, which implies how to narrow a query, but it never says when to use this tool versus get_relation, evidence_between, or find_contradictions. Usage is inferable rather than stated.

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

Deploy Server

Other Tools