Rank stored facts by PageRank to surface load-bearing decisions that later facts build on. Retrieve the top foundational facts from a shared graph memory.
Rank facts by PageRank (FalkorDB graph algorithm). The top facts are the load-bearing decisions that later facts kept building on.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It explains the ranking algorithm and the semantic meaning of top facts, but omits operational behavior such as read-only status, default limit, pagination, or return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action, and no filler. The second sentence adds useful semantic context without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description should explain return structure and usage context. It provides a conceptual overview but omits what the output looks like, default behavior, and when to choose this tool over siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one optional parameter (limit) with 0% description coverage. The description never mentions limit, its default, or its effect, adding no meaning beyond the bare type and constraints in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Rank') and resource ('facts') and explains the ranking method (PageRank) and the semantic meaning of top facts. It distinguishes from siblings like relay_get_context or relay_get_briefing by focusing on ranked importance, though it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance or alternatives. It does not say when to prefer this over relay_get_briefing, relay_get_impact, or relay_get_clusters, leaving the agent to infer from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.