List a memory's links one page at a time, following next_offset to retrieve the next set of relations or diagrams.
List a memory's links, one page at a time; follow next_offset.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | the memory. | |
| part | No | 'relations' (edges, both ways) or 'diagrams' (flows pointing at it). | relations |
| offset | No | where the page starts; `next_offset`, when present, starts the next. |
Changes observed during successful MCP inspections.
v0.16.1Input schema / properties / offsetAdded value: +{
+ "default": 0,
+ "description": "where the page starts; `next_offset`, when present, starts the next.",
+ "type": "integer"
+}Input schema / properties / partAdded value: +{
+ "default": "relations",
+ "description": "'relations' (edges, both ways) or 'diagrams' (flows pointing at it).",
+ "type": "string"
+}Input schema / properties / uid / descriptionAdded value: +"the memory."Input schema / properties / uid / titleRemoved value: -"Uid"Input schema / titleRemoved value: -"get_relationsArguments"Output schema / (root)Previous value: -{
- "properties": {
- "result": {
- "items": {
- "additionalProperties": true,
- "type": "object"
- },
- "title": "Result",
- "type": "array"
- }
- },
- "required": [
- "result"
- ],
- "title": "get_relationsOutput",
- "type": "object"
-}New value: +nullv0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that results are paginated and driven by next_offset, which is genuinely useful behavioral context, but that same mechanism is already spelled out in the offset schema description, so the marginal value is modest. No error or empty-result behavior is described.
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?
A single compact sentence that front-loads the core action ('List a memory's links') and ends with the actionable pagination hint. No filler.
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?
For a simple three-parameter read tool with full schema coverage and annotations covering safety, the description is nearly complete. The one remaining gap is return shape — there is no output schema, and while 'follow next_offset' hints that next_offset appears in the response, the description does not describe the returned link records.
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?
Schema description coverage is 100% — uid, part (with its enum-like values 'relations'/'diagrams'), and offset are all documented in the schema. The description adds no syntax, format, or defaulting detail beyond that, so the baseline 3 applies.
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 and resource: 'List a memory's links'. This is clearly distinguishable from write-oriented siblings like link_memories or get_memory, though it never names an alternative explicitly. The 'one page at a time' scope note sharpens the purpose further.
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?
Usage is implied by the purpose (use it when you need a memory's links) and the pagination instruction tells the agent how to continue iterating. However, there is no explicit when-to-use/when-not guidance, no statement of prerequisites (e.g., a valid uid), and no pointer to alternatives like search or get_memory for related lookups.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.