Skip to main content
Glama
Sign In

HypePaper

by app.hypepaper
OverviewDiscussionsAdmin

expert_wiki

The expert's wiki: one structural page per public node (papers, concepts, entities, topics, questions, syntheses) with its description and every relation in and out. Without slug: list pages (filter with q) and counts per kind. With slug: the page body. Use for a readable dossier on one thing; use expert_search_facts to find claims. [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": {
      "topic_id": "<topic_id>"
    },
    "name": "expert_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSubstring filter on title/slug.
slugNoPage slug from the listing.
topic_idYesTopic id of an expert (from list_experts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it does disclose the two response shapes: a listing with per-kind counts on one path, and description plus every in/out relation on the other. It also flags the cost ("Free · 1 credit") and that only public nodes appear. Not stated: error behavior for an invalid or private slug, and whether the relation list is truncated.

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?

Three compact clauses front-load the resource, then the branch behavior, then the routing advice and cost tag. Nothing is repeated from the schema verbatim and no sentence is filler.

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?

There is no output schema, so the description must describe returns, and it does: counts per kind for the listing, description and all incoming/outgoing relations for the page. For a 3-parameter read tool this covers everything an agent needs to call it correctly.

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 coverage is 100%, so the baseline is 3; the description adds real meaning by making slug a mode switch (present = page body, absent = listing) and by tying q to the listing mode with a substring filter on title/slug. It does not, however, describe what happens if slug is combined with q.

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?

Names a specific resource (the expert's wiki, one structural page per public node) and spells out the two shapes of the operation: listing when slug is absent, page body when present. It also explicitly separates itself from expert_search_facts, so an agent can choose without opening the schema.

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?

Gives an explicit when-to-use ("a readable dossier on one thing") and a named alternative for the different need ("use expert_search_facts to find claims"). The slug/no-slug branch tells the agent which mode of the same tool applies.

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