Librarian MCP Server

organize_library

Organize documents by applying AI-driven patterns and mental models. Choose scope, strategy, and method to categorize, tag, or structure your library.

Instructions

Organize documents using AI-driven patterns and mental models

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": {
      "scope": "<scope>",
      "strategy": "<strategy>",
      "method": "<method>"
    },
    "name": "organize_library"
  }
}

Input Schema

Name	Required	Description
`scope`	Yes	Scope of documents to organize
`method`	Yes	Organization method to apply
`options`	No
`strategy`	Yes	Organization strategy

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as modification permissions, destructive nature, or side effects. The dryRun option in the schema implies preview capability, but this is not highlighted in the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence) but lacks detail and could be more tailored to the tool's complexity. It is not verbose, but it is too brief to be fully informative.

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

Completeness2/5

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

Given the tool's complexity (4 parameters, 3 enums, nested object, no output schema), the description is insufficient. It does not explain return values, organization methods, or the AI-driven process.

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 high (75%), so the schema itself documents parameters adequately. The description adds no additional meaning beyond what the schema provides.

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 organizes documents using AI-driven patterns, and it distinguishes from siblings like delete or search. However, it lacks specificity about what 'patterns and mental models' means.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, context, or exclusions.

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

Deploy Server