Skip to main content
Glama

List memory share links

list_memory_shares
Read-only

Use this when the user asks which share links exist for the connected vault, or needs a share id to revoke. Lists each link with its status, memory count, uses and expiry. Never returns links, passwords or memory keys.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_memory_shares"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sharesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuinely new behavioral context in stating what is never returned (links, passwords, memory keys), which matters for a secrets-adjacent tool. It says nothing about pagination, ordering, or behaviour when no links exist, leaving a modest gap.

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?

Three tight sentences, each doing distinct work: when to call, what is returned, and what is deliberately withheld. The trigger condition is front-loaded and there is no redundant restatement of the tool name.

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 zero-parameter read-only tool with annotations and an output schema, the description covers the essentials: trigger, return shape summary, and a notable security caveat. Only the empty-result and ordering behaviour are left unstated, which is a minor omission given the output schema carries field detail.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 would apply. Slightly discounted because the sole parameter-like concept, the 'connected vault' scope, is mentioned but never explained or constrained, leaving a small unresolved ambiguity about which vault is consulted.

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?

States a specific verb and resource ('Lists each link' for 'the connected vault') and enumerates the fields returned (status, memory count, uses, expiry). An agent can immediately distinguish this from create_memory_share, revoke_memory_share or import_memory_share because the resource and the read-only nature are explicit.

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

Usage Guidelines4/5

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

Gives two concrete trigger conditions: the user asks which share links exist, or a share id is needed before revoking. That covers the main invocation contexts, including the natural hand-off to revoke_memory_share. It stops short of an explicit exclusion clause, so it lands just under the top band.

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