Data Platform MCP

Overview Schema Source Related Servers Discussions Admin

list_indexed_documents

List indexed documents, optionally filtered by connection and domain, to view your data platform's available information.

Instructions

List indexed documents, optionally restricted to connection and/or domain.

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_indexed_documents"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	No
`connection_id`	No

Output Schema

Name	Required	Default
`total`	Yes
`documents`	Yes
`contract_version`	No	1.0.0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Aug 5, 2026

TDQS

B3.3/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 for behavioral disclosure. It indicates a read-only operation but lacks details on pagination, result size, ordering, or permissions. The description does not even clarify whether it returns document summaries or full content.

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 that is front-loaded with the core action and resource. Every word is purposeful, with no redundancy or irrelevant detail.

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?

The tool is simple (2 optional params) and has an output schema, so return values are adequately covered externally. However, the description lacks behavioral context like pagination and does not explicitly differentiate itself from search_documents. It is minimally viable but leaves room for improvement.

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 0%, but the description adds meaning by mentioning 'connection and/or domain,' which maps to the connection_id and domain parameters. However, it does not specify the value format or how the filters combine (AND vs OR), leaving ambiguity.

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 action ('List') and the resource ('indexed documents'), with explicit optional filters ('connection and/or domain'). It distinguishes itself from sibling tools like search_documents and delete_indexed_document by its specific focus on listing indexed documents.

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?

There is no guidance on when to use this tool versus alternatives such as search_documents or refresh_document_index. The description simply states the function without contextualizing its role among the sibling tools, leaving the agent to infer usage.

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