Skip to main content
Glama

mu

by mu.micro

Browse docs

docs_list
Read-onlyIdempotent

List your documents, most recently changed first, with an optional search over titles and bodies. Use this to find an id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum documents to return (default 50)
queryNoOptional text to match against titles and bodies

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changed
    • removedInput schema / properties / collection
      Removed value: -{
-  "description": "Collection name",
-  "type": "string"
-}
    • changedInput schema / properties / limit / description
      Previous value: -"Max records to return (default 50, max 200)"New value: +"Maximum documents to return (default 50)"
    • removedInput schema / properties / order
      Removed value: -{
-  "description": "\"asc\" or \"desc\" (default desc)",
-  "type": "string"
-}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Optional text to match against titles and bodies",
+  "type": "string"
+}
    • removedInput schema / properties / scope
      Removed value: -{
-  "description": "\"mine\" (default), \"public\", or \"all\" for both",
-  "type": "string"
-}
    • removedInput schema / properties / sort
      Removed value: -{
-  "description": "Data field to sort by",
-  "type": "string"
-}
    • removedInput schema / properties / where
      Removed value: -{
-  "description": "Filter on data fields, e.g. {\"done\": false, \"priority\": {\"gte\": 2}}",
-  "type": "object"
-}
    • removedInput schema / required
      Removed value: -[
-  "collection"
-]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnly and idempotent hints, so the description adds behavioral value by specifying sort order ('most recently changed first') and search scope ('over titles and bodies'). No contradiction with annotations.

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?

Two concise sentences, front-loaded with the action and result, and no unnecessary content.

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?

The description covers ordering, search, and use case, with parameters well-documented in the schema. Slight gap: it doesn't explicitly state that the returned list includes document ids, though it implies them via 'find an id'.

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 covers 100% of the parameters with descriptions. The description's phrase 'search over titles and bodies' merely restates the schema's query description, adding no new parameter semantics.

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 it lists documents, sorted by most recent change, with optional search. It effectively distinguishes from sibling tools like docs_read or docs_write by focusing on browsing to find an id.

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

Usage Guidelines4/5

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

Explicitly tells the agent to use this to find an id, which is a clear use case. It doesn't explicitly mention alternatives or when not to use it, but the context is sufficient for simple selection.

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

All mu toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation5/5

Every tool is prefixed with a clear domain (e.g., apps_, blog_, transit_), and the suffix identifies a distinct action or resource. Overlapping tools like archive_search and news_search are explicitly differentiated in their descriptions.

Naming Consistency4/5

All tools consistently use a domain_prefix_suffix pattern, but the suffix is sometimes a verb (create, list, search) and sometimes a noun (inbox, status, address). This minor mixing prevents a perfect score but remains predictable and readable.

Tool Count2/5

With 113 tools, the count is far beyond the typical well-scoped range, even for a broad personal assistant. While each tool is distinct and serves a purpose, the sheer number is overwhelming and could be better organized into separate domain-specific servers.

Completeness4/5

Each domain has near-complete lifecycle coverage, including CRUD and search where relevant, with only minor gaps such as missing apps_delete or events_update. The wide range of covered domains itself demonstrates strong completeness for a general assistant.

Resources