Skip to main content
Glama

get_knowledge_tree

Retrieves a knowledge tree of research communities across time windows, showing citation and similarity links to reveal how communities emerged and which earlier work they build on.

Instructions

Knowledge tree: papers per community in each time window, and links from earlier to later windows weighted by citations and by S3 similarity links. Use it to describe how communities emerged, which earlier work each one builds on, and where knowledge flowed.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_knowledge_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
min_linksNo
window_yearsNo
n_communitiesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the shape of the produced data (per-window community paper sets plus weighted inter-window links), which tells the agent what it is getting. It says nothing about cost, result size, whether links are pruned by a threshold, or permissions, so significant behavioral gaps remain.

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 what the tool returns and followed by intended analyses; there is no filler. The first sentence is dense and stacks several concepts, but every clause carries information.

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?

An output schema exists, so return values need not be spelled out, and the description covers the analytical intent well. The gap is on the input side: four parameters with zero schema documentation and no explanation of what tuning them changes, which is a meaningful omission for a tool with configurable windows, community counts, and link thresholds.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description is the only source of meaning and it mostly falls short. Phrases like 'each time window' and 'papers per community' loosely gesture at window_years and n_communities, but run_id and min_links are never addressed, and no parameter is given range, default behavior, or effect on output.

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 names a concrete resource and its contents: papers per community per time window, plus citation- and S3-weighted links from earlier to later windows. The retrieval verb is implicit in the name rather than stated, and no sibling (e.g. get_citation_structure or get_community) is named as a contrast, so an agent must still infer how this differs from those.

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?

It gives a use case in analytical terms — describing how communities emerged, what earlier work they build on, and where knowledge flowed — which implies when to reach for it. However, there is no when-not guidance, no prerequisite mentioned (besides the required run_id), and no alternative tool named for related questions.

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