Skip to main content
Glama

Get Research Direction

get_direction
Read-onlyIdempotent

Retrieve a research direction's context—leading authors, key papers, and adjacent directions—from a cluster ID or URL to answer who works on or what surrounds a topic.

Instructions

Describe one research direction: what it is, who leads it, what is nearby.

Use for "who works on X", "what is the state of X" and "what is adjacent to X", after search_lacuna(search_type="cluster") finds the direction. The context names the direction's leading authors, key papers and related directions.

Use a numeric cluster ID (for example 25005) or a direction URL ending in that number.

view selects the response shape (context typically contains the fields full provides plus the agent-oriented summary content):

  • "context" (default, recommended): compact agent-oriented summary with summary_markdown, capped papers/authors/related_directions, and truncation markers.

  • "full": raw upstream cluster record only. Cheaper than context when you only need basic cluster metadata.

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": {
      "cluster_id_or_url": "<cluster_id_or_url>"
    },
    "name": "get_direction"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNocontext
cluster_id_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds substance they do not: the accepted identifier format, what the context payload contains (summary_markdown, capped papers/authors/related_directions, truncation markers), and a relative cost signal ("full" is cheaper than "context"). Truncation markers and cost hints are exactly the operational details annotations cannot express.

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?

Front-loaded with the purpose, then usage, then input format, then per-value view semantics — a sensible order with no filler sentences. The parenthetical claiming context "typically contains the fields full provides plus the agent-oriented summary" is hedged and slightly muddled, costing it the top score.

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

Completeness5/5

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

Two parameters, one optional, and both are fully explained; the output schema existence means return values need no further enumeration, yet the description still characterizes the payload and its truncation behavior. Nothing an agent needs in order to call this correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the load and it does: cluster_id_or_url is documented as a numeric cluster ID or a direction URL ending in that number, with a concrete example (25005). The view enum values are each explained with content and cost tradeoffs, well beyond what the bare enum in the schema conveys.

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 plus the facets returned ("what it is, who leads it, what is nearby"), which an agent can map onto a user question. It also positions the tool downstream of search_lacuna(search_type="cluster"). It stops short of contrasting against the closest siblings such as get_direction_papers or get_author_directions, so a 4 rather than a 5.

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

Usage Guidelines5/5

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

It names the exact query patterns the tool serves ("who works on X", "what is the state of X", "what is adjacent to X") and states the prerequisite that search_lacuna must have already found the direction. It also tells the agent which view to pick and when, giving a complete when-to-use picture.

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