Skip to main content
Glama
Sign In

HypePaper

by app.hypepaper
OverviewDiscussionsAdmin

library_node_context

Your personal library: Fetch a node's neighborhood subgraph (nodes + edges) at the given depth. Use to expand context around a specific node id you've already located. [Free · 1 credit]

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": {
      "node_id": "<node_id>"
    },
    "name": "library_node_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo
node_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns nodes and edges and notes the cost, but it omits depth limits, node id format, and any operational constraints such as rate limits or library scoping.

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 and compact: it states the tool's purpose, usage context, return shape, and cost in two short sentences with no wasted wording.

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 a two-parameter graph expansion tool with no output schema and no annotations, the description covers the core purpose and return shape. However, it leaves out depth semantics and other invocation-relevant details that would help an agent call it correctly beyond the default.

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

Parameters3/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 explain both parameters. It usefully implies that node_id comes from a prior lookup and that depth controls neighborhood radius, but it does not specify valid depth values or the expected node id format.

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 states a specific verb and resource: fetch a node's neighborhood subgraph containing nodes and edges. It also distinguishes the operation from search by specifying that the node id has already been located.

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 explicitly says to use this tool to expand context around an already-located node id. It does not name when not to use it or call out alternative sibling tools, but the intended context 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