Skip to main content
Glama
Sign In
Coda MCP Server

Coda MCP Server

by orellazri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coda_list_documents

Search and list all available Coda documents. Use an optional query to filter results.

Instructions

List or search available documents

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": "coda_list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoThe query to search for documents by - optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.2/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. 'List or search' implies a read operation, but it does not disclose authentication needs, pagination, or what 'available' means. It also does not describe the return format, which is needed since there is no output schema.

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, front-loaded sentence with no wasted words. It economically conveys the core function and allows the schema to handle parameters.

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?

The tool is simple (one optional parameter, no output schema), but the description omits what the returned documents look like or how 'available' is defined. Given the sibling list tools, more context would help the agent understand what distinguishes a document and when to use this tool first.

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 coverage is 100% and the single parameter 'query' has a clear description. The tool description adds no additional semantic information beyond implying that 'query' is used for searching, which is already in the schema. 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?

The description clearly states the tool's purpose with specific verbs ('list' or 'search') and resource ('documents'). It distinguishes from sibling tools like coda_list_pages, coda_list_tables, and coda_list_rows by focusing on documents rather than pages/tables/rows.

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 is provided on when to use this tool versus alternatives. With many sibling list tools, the description does not explain when to choose list_documents over list_pages or list_tables, or mention any prerequisites or context.

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