Psychedelics Knowledge Graph

find_relationships

Search deduplicated paper-level concept relationships.

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

Input Schema

Name	Required	Description	Default
`dois`	No
`limit`	No
`cursor`	No
`domains`	No
`year_to`	No
`paper_ids`	No
`year_from`	No
`author_ids`	No
`object_ids`	No
`concept_ids`	No
`paper_types`	No
`subject_ids`	No
`author_names`	No
`object_kinds`	No
`object_labels`	No
`subject_kinds`	No
`paper_subtypes`	No
`relation_types`	No
`subject_labels`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Search' implies a read operation and 'deduplicated' hints at result uniqueness, but the definition says nothing about default behavior with no filters, pagination via cursor/limit, ordering, permissions, or rate limits. For a 19-parameter search endpoint where all filters are optional, that is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words, so it is concise. But for a tool with 19 filters and no annotations, that brevity leaves it under-specified rather than appropriately sized.

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

Completeness1/5

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

The tool has 19 parameters, 0% schema description coverage, and no annotations; the description compensates for none of that. Although an output schema exists and need not be explained, the input semantics and usage context are almost entirely absent.

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

Parameters1/5

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

Schema description coverage is 0% across 19 parameters, and the description adds no parameter meaning at all. It does not explain what dois, paper_ids, concept_ids, relation_types, subject/object kinds, labels, domains, or year filters do, nor how they interact.

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?

The description gives a specific verb and resource: 'Search deduplicated paper-level concept relationships.' That is clearer than a tautology and tells the agent this is a relationship-search tool rather than a paper or concept lookup. It does not, however, distinguish itself from siblings such as search_papers or search_concepts, and 'concept relationships' remains somewhat opaque.

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

Usage Guidelines2/5

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

The description provides no when-to-use guidance, no when-not-to-use guidance, and no alternatives. With 19 optional filters and siblings like search_papers, search_concepts, and get_concept, an agent has no textual basis for choosing this tool over another.

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

All Psychedelics Knowledge Graph 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.