Skip to main content
Glama
Sign In

HypePaper

by app.hypepaper
OverviewDiscussionsAdmin

expert_graph_map

A budgeted subgraph around a query: seeds are the best full-text hits in the expert's graph, then neighbours join by how many edges tie them to what is already held, until budget nodes. Returns nodes, the edges among them and the papers they came from. Use for 'what surrounds X in this field' in one call; then expert_node_context to go deeper. [Free · 2 credits]

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": {
      "topic_id": "<topic_id>",
      "query": "<query>"
    },
    "name": "expert_graph_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
budgetNo
topic_idYesTopic id of an expert (from list_experts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it explains the seed-and-expand algorithm, the role of the budget cap, the returned contents (nodes, edges, source papers), and the credit cost. It does not cover edge cases such as zero hits or rate limits, but the core read-only behavior is transparent.

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?

The description is front-loaded, dense with useful information, and free of filler. Each sentence contributes either purpose, mechanics, return shape, usage routing, or cost.

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 moderately complex graph traversal tool without an output schema, the description explains the return shape and the algorithm sufficiently for correct invocation. Minor gaps around edge cases and exact output structure remain, but the essential context is present.

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 33%, but the description compensates by clarifying that `query` drives full-text seed selection, `budget` caps the number of nodes, and the graph belongs to an expert identified through `topic_id`. It adds meaningful semantics beyond the parameter names and constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies a specific operation: constructing a budgeted subgraph around a query, with seeds from full-text hits and expansion by edge connectivity. It also distinguishes the tool from expert_node_context by positioning that sibling as the deeper follow-up.

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

Usage Guidelines4/5

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

It gives a concrete use case ('what surrounds X in this field') and states that this tool should be used for that in one call, then points to expert_node_context for deeper exploration. It lacks explicit when-not guidance, but the routing to an alternative is clear.

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

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