Skip to main content
Glama
Sign In

Ilu Rennik

by com.ilurennik
OverviewDiscussionsAdmin

Shelves: add, name, hide, or make one of the owner's own

shelf
Destructive

Shelves of facts, such as insurance, accounts, health and documents: see or change. Use this when the person wants to see, name, hide or make a shelf, or put facts on a shelf of their own. Do not use for moving one fact to a standard shelf; that is change with do move. The owner's shelves as they are named on their screen. do: list (names, and which are hidden); rename, hide, show, add (a standard shelf on their screen, even while empty); create (a shelf of their own called name); put and take (facts, by id, onto or off their own shelf); remove (their own shelf, for good; its facts stay on their shelves). Before a seat is given, list shows the owner what each shelf holds. The name is the owner's.

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": {
      "do": "<do>",
      "owner_said": "<owner_said>"
    },
    "name": "shelf"
  }
}

Input Schema

NameRequiredDescriptionDefault
doYeslist names each shelf and which are hidden. rename, hide, show and add change a standard shelf on their screen. create makes a shelf of their own. put and take move facts onto or off their own shelf. remove removes their own shelf for good, and its facts stay on their shelves.
nameNoThe new name, for rename or create.
partNoWhich part of a long answer to read: the answer's `next_part`. Leave it out for the first.
factsNoFact ids, for put or take.
shelfNoThe shelf, by the name on their screen or the name they gave it.
owner_saidYesThe owner's message this call is based on, verbatim as they wrote it. It is the receipt for what is written; a quote, statement or answer passed with it must appear in it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses that `remove` is permanent but leaves the shelf's facts in place, that `list` reveals hidden shelves, and that `add` can create an empty standard shelf. It does not describe permissions, error behavior, or return details for every operation, but it adds meaningful behavior that the annotations alone do not provide.

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?

The description is front-loaded with purpose and usage, then moves into operation details. It is somewhat repetitive with the `do` schema, and phrases like “The name is the owner's” are not essential, but the structure remains useful for a multi-action tool.

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 nine-action, six-parameter tool with no output schema, the description covers all major operations and the key destructive consequence of `remove`. It leaves some lower-level details to the schema, such as `part` pagination and `owner_said`, which is appropriate given the high schema coverage.

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 the schema already documents the parameters, including the `do` enum values. The description restates the `do` semantics but adds little parameter-level meaning beyond the schema, so the baseline score 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?

The description names the resource (shelves of facts) and a concrete set of operations: see, name, hide, make, put, take, remove. It also explicitly distinguishes this tool from `change` for moving one fact to a standard shelf, so an agent can route correctly without opening the schema.

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?

It gives an explicit when-to-use statement and a when-not-to-use statement naming the sibling alternative (`change` with do move). The individual `do` operations are also enumerated with their intended use.

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

All Ilu Rennik 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