Skip to main content
Glama
Sign In

Memorables

by es.memorabl
OverviewDiscussionsAdmin

Create a collection

create_collection

Create a new collection in the signed-in member's account, public unless private is asked for. Only when the person asks for it. Then add works with add_to_collection.

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

Input Schema

NameRequiredDescriptionDefault
nameYesIts name (80 characters at most).
privateNotrue for a collection only the member sees. Public by default.
descriptionNoA sentence about it (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write. The description adds real value beyond them: the public-by-default visibility outcome, the user-consent requirement, and the recommended next step. It does not cover duplicate-name handling or what callers receive back.

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 short sentences, front-loaded with the action and scope, then the consent condition, then the next step. No filler and nothing buried; the telegraphic phrasing of "Only when the person asks for it" stays readable in context.

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 small three-parameter write with no output schema, the definition covers purpose, default state, and the follow-up path. It omits what the call returns (the new collection's identifier), which the agent would need to chain into add_to_collection.

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%, so all three parameters (name, private, description) are already documented with lengths and defaults. The description only restates the private/public default, adding no syntax or format guidance beyond the schema; baseline 3 applies.

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 ("create a new collection") plus its scope ("in the signed-in member's account") and the default visibility rule. The agent can distinguish it from add_to_collection or get_collection without inspecting either schema.

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?

"Only when the person asks for it" gives a clear consent-based condition for invoking, and "Then add works with add_to_collection" names the correct follow-up sibling. It stops short of stating when NOT to use it (e.g., when a matching collection already exists).

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

All Memorables toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources