Skip to main content
Glama
Sign In
JauMemory MCP Server

JauMemory MCP Server

Official
by Jau-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_collection

Retrieve details of a specific collection, including all its memories, by providing the collection's UUID.

Instructions

Get details of a specific collection including all its memories.

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": {
      "collection_id": "<collection_id>"
    },
    "name": "get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collection_idYesUUID of the collection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. However, it only states it returns 'details of a specific collection including all its memories' without clarifying whether the operation is read-only, what 'memories' refers to, or any side effects. Contrast this with a readOnlyHint annotation that would alleviate the concern, but none exist.

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 a single, concise sentence that directly conveys the tool's purpose without extra words. It is perfectly front-loaded.

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?

Given the tool has one parameter, no output schema, and no annotations, the description is adequate for a simple read operation but lacks detail on the response format or what 'details' includes. It does mention 'memories', which is useful context.

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 100% with one parameter (collection_id) described as 'UUID of the collection'. The tool description doesn't add any new meaning beyond what's in the schema, but high coverage means the schema carries the burden, earning a baseline 3.

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 clearly states the tool retrieves details of a specific collection including its memories, using the verb 'Get' with a specific resource ('collection'). This distinguishes it from siblings like get_guide or list_collections, though some siblings (e.g., update_collection, delete_collection) share the collection focus, so it's not fully differentiated from all.

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?

No guidance is provided on when to use this tool versus alternatives like list_collections (list all collections) or search (general search). It doesn't state prerequisites (e.g., collection must exist) or when not to use it.

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