Skip to main content
Glama
Sign In
Kiseki-Labs-Readwise-MCP

Kiseki-Labs-Readwise-MCP

by kiseki-technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

find_readwise_documents_by_names

Search for specific documents in Readwise using document names. Returns matching Book objects or indicates when documents are not found.

Instructions

Find documents in Readwise by a list of names.

Args:
    document_names (List[str]): The names of the documents to search for in Readwise.

Returns:
    Dict[str, Optional[Book]]: A dictionary where keys are the requested document names
    and values are the corresponding Book objects if found, or None otherwise.

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

Input Schema

NameRequiredDescriptionDefault
document_namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 full burden. It discloses the return format (dictionary with Book objects or None) but lacks critical behavioral details such as whether this is a read-only operation, error handling for invalid names, performance implications, or authentication needs. The description adds some value but is insufficient for a mutation-sensitive context.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured Args and Returns sections. Every sentence adds value without redundancy, making it efficient and easy to parse.

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?

Given no annotations, no output schema, and low schema coverage, the description is moderately complete. It covers the basic purpose, parameter semantics, and return format, but gaps remain in behavioral transparency and usage guidelines. For a tool with one parameter and no complex outputs, it meets minimum viability but could be more comprehensive.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'document_names' is a list of strings used to search for documents in Readwise, clarifying the parameter's role beyond the bare schema. However, it does not detail constraints like name formatting or case sensitivity.

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 verb 'find' and resource 'documents in Readwise', specifying it searches by 'a list of names'. It distinguishes from siblings that filter by IDs or other criteria, though not explicitly named. The purpose is specific but could be slightly more precise about differentiation.

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

Usage Guidelines3/5

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

The description implies usage when searching by document names, as opposed to siblings that use IDs or filters, but does not explicitly state when to use this tool versus alternatives. No exclusions or prerequisites are mentioned, leaving some ambiguity for the agent.

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