Skip to main content
Glama
Sign In
BoteX

BoteX

by kubainter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_backlinks

Retrieve all memories linking to a specified memory ID via wikilinks to discover backlinks for knowledge graph analysis.

Instructions

Finds all memories that link TO the given memory_id via [[wikilinks]].

Args:
    memory_id: Target memory ID (e.g. 'mem_a1b2c3d4').
    workspace_dir: Workspace root directory.
    scope: Lookup scope ('local', 'global', or 'all').

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": {
      "memory_id": "<memory_id>"
    },
    "name": "get_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNolocal
memory_idYes
workspace_dirNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.8/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 conveys that this is a retrieval operation and that it follows [[wikilink]] references, but it does not clarify scope semantics, missing-target behavior, or whether results are direct-only or transitive.

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 short, front-loaded with the core purpose, and then structured as a compact Args list. Every sentence adds useful information without repetition or filler.

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?

For a simple read-only retrieval tool with an output schema, the definition is largely complete: it explains the operation and all parameters. It is missing richer usage guidance and scope behavior details, but those gaps are moderate rather than blocking.

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 description coverage is 0%, so the description must compensate by documenting all three parameters. It gives an example memory_id format, identifies workspace_dir as the root directory, and enumerates the allowed scope values, though it does not explain the practical difference between 'local', 'global', and 'all'.

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: it finds all memories that link TO the given memory_id via [[wikilinks]]. The directionality of the lookup makes it distinguishable from sibling memory tools such as search_memory or read_memory.

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

Usage Guidelines2/5

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

The description explains what the tool does but gives no explicit guidance on when to use it versus alternatives like search_memory or find_graph_health. There are no exclusions, prerequisites, or usage conditions.

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

Deploy Server

Other Tools