Skip to main content
Glama

Explore card relationships

get_card_neighborhood
Read-onlyIdempotent

Read a page of the selected owner card’s confirmed private relationships and inferred shared-tag connections. Results are bounded and read-only.

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": {
      "item_id": "<item_id>"
    },
    "name": "get_card_neighborhood"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
item_idYes

Output Schema

NameRequiredDescriptionDefault
edgesYes
nodesYes
truncatedYes
next_cursorYes
center_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real behavioral context beyond the annotations: results are bounded (paging is required to enumerate), relationships are scoped to the caller's private view, and it distinguishes confirmed edges from inferred shared-tag edges — a confidence distinction an agent would otherwise have to guess.

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?

Two short sentences with no filler; the data scope (confirmed vs inferred) is front-loaded and the read-only/bounded caveat follows immediately. Every clause carries information.

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?

Output schema exists, so return-value explanation is unnecessary, and the description covers the meaningful semantics for a simple two-parameter read: data type, confidence tiers, privacy scoping, and bounded paging. Only the item_id vs cursor distinction is left to inference.

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 carries the burden for both params. It partially compensates: "a page" plus "results are bounded" signals cursor pagination, and "selected owner card" identifies item_id as the card identifier. Neither parameter is named or given format guidance, so the mapping must be inferred.

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

Purpose4/5

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

Names a specific verb and resource: it reads the confirmed private relationships plus inferred shared-tag connections for one owner card, so an agent knows exactly what data comes back. It is not explicitly separated from retrieval siblings like search_card_browser, but the relationship-graph framing is distinctive enough to disambiguate in practice.

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

Usage Guidelines3/5

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

The phrase "selected owner card" implies a precondition (a card must already be chosen) and the tool is clearly the graph-expansion step, but there is no explicit when-to-use/when-not guidance and no named alternative for other card lookups. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.