Skip to main content
Glama
mitchuski

agentprivacy

by mitchuski

guide.neighbours

guide_neighbours

Retrieve linked pages and backlinks for a given page, enabling navigation to adjacent nodes in the lattice.

Instructions

Linked pages (outgoing and backlinks) of a page, each with the NAMED LATTICE MOVE from this page to it: succ · neg · bnot · flip · jump ×k (dimensions), per the 64-vertex sovereignty lattice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNo
slugYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose side effects, permissions, data mutation, rate limits, or whether the operation is read-only. The agent is given no behavioral expectations beyond an unclear statement about linked pages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but poorly structured and filled with unexplained jargon like 'succ · neg · bnot · flip <dimension> · jump ×k'. The opening phrase is somewhat concise, but the rest detracts from clarity and does not effectively front-load useful information.

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

Completeness1/5

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

The description omits essential context such as the return format, the meaning of the lattice moves, the relationship between parameters and the page, and any example usage. With no output schema and cryptic terminology, the tool is not sufficiently specified for reliable invocation.

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

Parameters1/5

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

The schema lists 'site' and 'slug' with no descriptions, and the tool description does not explain what these parameters mean or how they relate to the 'page'. Schema coverage is 0%, and the description provides no meaningful parameter semantics.

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

Purpose2/5

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

The description states the tool deals with 'linked pages (outgoing and backlinks) of a page', but it is phrased as a noun phrase rather than a clear action. The appended 'NAMED LATTICE MOVE' terminology is cryptic and does not clarify the tool's primary purpose or distinguish it from sibling tools like guide_search or guide_page.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the sibling tools. The description does not mention alternatives, conditions, or scenarios, leaving the agent to infer usage solely from the tool name and vague description.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mitchuski/agentprivacy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server