weReci

Reimagine the curated shelves

reshuffle_conceits

Regenerate the collection's curated shelves ("conceits") — a fresh themed re-grouping of every entry, replacing the current shelves. BEFORE calling: confirm the user actually wants a reshuffle, and ask whether they'd like to give the curation a creative direction (a theme, mood, or organizing idea — e.g. "lean into late-summer produce"). Pass their answer as guidance, or omit it for a clean-slate shuffle. The run takes about a minute in the background; call list_conceits afterwards to see the new shelves.

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": "reshuffle_conceits"
  }
}

Input Schema

Name	Required	Description	Default
`guidance`	No	Optional creative direction from the user for the new shelves.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate mutation (readOnlyHint false) and non-destructive (destructiveHint false). Description adds that it runs in the background (~1 min) and replaces existing shelves, and suggests follow-up. Adds behavioral context beyond annotations.

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?

Moderately long but every sentence adds value; purpose is front-loaded and instructions are clear. No fluff.

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

Completeness5/5

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

For a single-optional-parameter tool with no output schema, the description covers the full call sequence: confirm, ask for direction, pass guidance, wait, and verify with list_conceits. An agent has everything needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already covers guidance with a description; description adds how to populate it (pass user's answer or omit for clean slate), making the parameter's use explicit.

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 (regenerate) and resource (curated shelves/conceits), and explains that it replaces current shelves. Distinguishes from sibling list_conceits which is a read-only view.

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

Usage Guidelines5/5

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

Explicitly instructs to confirm user intent and ask for creative direction before calling, and provides the guidance parameter usage. Also tells to call list_conceits afterwards. Gives clear when-to-use context.

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

All weReci tools Inspect

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

Need Help?