Skip to main content
Glama

Link a related memory

place

Link a concept to another so it shows up in that concept's [ YOU MAY ALSO NEED ] list of related memories, at a given rank (1 is the top).

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": {
      "suggested": "<suggested>",
      "list_owner": "<list_owner>",
      "rank": "<rank>"
    },
    "name": "place"
  }
}

Input Schema

NameRequiredDescriptionDefault
rankYesPosition in the list; 1 is the top.
suggestedYesThe concept to suggest.
list_ownerYesThe concept whose list it goes into.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety framing is covered. The description usefully adds where the link surfaces (the related-memories list) and the rank ordering, but says nothing about what happens if the link already exists, whether an existing entry is overwritten or reordered, or whether the change is reversible.

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

Conciseness4/5

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

A single front-loaded sentence that leads with the action and effect, with the rank convention stated inline. The bracketed [ YOU MAY ALSO NEED ] formatting is slightly noisy but conveys the exact UI location, so it earns its place.

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

Completeness3/5

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

For a three-parameter mutation with full schema coverage and safety annotations, the description covers purpose and visible outcome adequately. It stops short of describing duplicate handling, rank collisions, or failure modes, which an agent would want before invoking a write operation.

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 coverage is 100% and every parameter is documented, so the baseline is 3. The description earns an extra point by clarifying the directional semantics: 'suggested' is what gets linked into 'list_owner', which the terse schema labels ('The concept to suggest') do not make fully obvious.

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?

The description states a specific verb (link) and resource (a concept to another) and explains the observable outcome: the concept appears in the target's [ YOU MAY ALSO NEED ] list. It does not explicitly contrast with the inverse operation 'cut' or with 'set_concept', so sibling differentiation is left implicit, but the effect is unambiguous.

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?

Usage is only implied by describing the resulting behavior; there is no explicit 'use this when' clause, no mention of prerequisites (both concepts must already exist), and no pointer to alternatives such as 'cut' for removing a link or 'create_concept' for making new ones.

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.

Resources