Skip to main content
Glama

Typebar (formerly SuperDocs)

list_documents

List the authenticated user/org's saved documents, most-recently-updated first (metadata only — no document content). Each carries a session_count ("N chats"). Documents become durable + reusable automatically as you create or edit them; on the FIRST call we also one-time import the documents of pre-Files-view chats so prior work appears here too. Pass archived=true to browse the soft-deleted set (the Files "Archived" filter).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of documents to return.
offsetNoOffset for pagination.
archivedNoWhen true, list your ARCHIVED (soft-deleted) documents instead of the live set — backs the Files view's Archived filter. Restore one with POST /v1/documents/{document_id}/unarchive.
include_previewNoInclude a small preview_html (first chunks) per document for thumbnails. The web Files view sets this; agents leave it off to stay token-light.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does disclose real behavior: result ordering, that only metadata is returned, and — most valuably — that the FIRST call triggers a one-time import of pre-Files-view chats. That side effect is exactly the kind of non-obvious trait an agent needs. It stops short of stating pagination defaults or whether the import is expensive/slow.

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?

Front-loads the core action and scope before the caveats, and every sentence carries information (ordering, metadata-only, session_count, import behavior, archived filter). The first-call import sentence is denser than needed but earns its place by disclosing a side effect.

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?

There is no output schema, so the description must convey returns — it does so partially by naming 'metadata only' and the session_count field, though it never enumerates the other document fields a caller will receive. Combined with full parameter coverage in the schema, this is nearly complete but leaves the response shape under-described.

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 limit, offset, archived and include_preview are already documented in structured data; the description mainly restates archived. It adds slight value by explaining that each row carries a session_count ('N chats'), but that is output shape rather than parameter meaning. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List the authenticated user/org's saved documents') plus scope and ordering ('most-recently-updated first'). The parenthetical 'metadata only — no document content' cleanly separates it from get_document_detail, a sibling an agent could otherwise confuse it with.

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 instructs 'Pass archived=true to browse the soft-deleted set', giving the condition that selects the archived variant. It does not name siblings like list_session_documents or get_document_detail as alternatives, so the routing is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.