Skip to main content
Glama
Sign In
whimsicality-mcp

whimsicality-mcp

Official
by WhimsicalityLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

whim_rag_index

Index a document by ID and text for keyword search retrieval. Add documents to make them searchable across sessions.

Instructions

Index a document for keyword search retrieval.

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": {
      "id": "<id>",
      "text": "<text>"
    },
    "name": "whim_rag_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument ID
textYesDocument text to index

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Index a document' without disclosing side effects, persistence, idempotency, or behavior on re-indexing with the same ID. This minimal disclosure offers little beyond the tool name.

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 sentence with zero wasted words. It front-loads the action and purpose efficiently, making it easy to parse quickly.

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 simple tool with two well-documented parameters and no output schema, the description is mostly complete. It covers the basic action and purpose. However, it could be improved by noting idempotency or overwrite behavior, but that is minor given its simplicity.

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 input schema fully describes both parameters (id and text) with 100% coverage, so the baseline for param semantics is 3. The description does not add extra meaning beyond the schema, but it also doesn't need to since the schema is sufficient.

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 clearly states the tool indexes a document for keyword search retrieval, which is a specific verb+resource action. It distinguishes from sibling tool whim_rag_search (which retrieves) and other whim_* tools by its unique purpose.

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 explicit guidance on when to use this tool versus alternatives, such as directing to index before calling whim_rag_search. The description implies indexing is a prerequisite but never states it directly or mentions exclusions.

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