Skip to main content
Glama

coda_list_docs

Read-onlyIdempotent

Retrieve a list of Coda docs with your API token, optionally filtering by name and limiting results to quickly locate relevant documents.

Instructions

List your Coda docs.

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": {
      "api_token": "<api_token>"
    },
    "name": "coda_list_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDocs to return (max 100, default 25)
queryNoFilter docs by name
api_tokenYesCoda API token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the possessive 'your', hinting at token-scoped results, but says nothing about pagination behavior, ordering, or what happens past the 100-doc cap.

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?

A single front-loaded sentence with zero filler. It is efficient, though the extreme terseness means there is no room for the operational detail an agent would benefit from.

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, the schema is fully documented, and annotations cover safety, so little is strictly missing for a correct call. However, with no output schema, the description gives no hint of the shape of the returned doc list, and the 100-item cap implicit in the limit parameter is left for the agent to discover.

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%, with limit (max 100, default 25) and query (filter by name) fully documented in the schema. The description adds nothing beyond that, which is the acceptable baseline given the schema does the work.

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?

States a specific verb and resource ('List ... Coda docs'), which is unambiguous and cleanly distinguishes it from siblings like coda_list_tables and coda_list_rows. It stops short of saying what a 'doc' scope covers or how it differs from any search-style alternative.

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 the sibling list tools, no mention of prerequisites beyond the required token, and no mention of the query/limit filtering options as an alternative path. The agent must infer usage entirely from the name.

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