Skip to main content
Glama

coda_list_tables

Read-onlyIdempotent

Lists the tables in a Coda document using an API token and doc ID, helping you retrieve table structure before querying or automating data workflows.

Instructions

List the tables in a Coda doc.

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>",
      "doc_id": "<doc_id>"
    },
    "name": "coda_list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesCoda doc id
api_tokenYesCoda API token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered externally. The description adds doc-scoping but says nothing about pagination, error behavior on a bad token/doc_id, or what a returned table entry contains. With annotations carrying the safety story, this is an adequate but thin 3.

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?

A single sentence with no filler, and the resource plus scope are front-loaded. There is nothing to trim.

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?

For a simple two-parameter read with full schema coverage and complete safety annotations and no output schema, the description covers what the tool does. The only meaningful omission is that the returned table identifiers are what feed coda_list_rows, which would help an agent chain calls.

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%: both doc_id and api_token are documented in the schema. The description only restates that tables belong to a doc, adding no format, ID-source, or auth-placement hints beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

The description gives a specific verb (List) and resource (tables) scoped to a Coda doc, which separates it from coda_list_docs. However, it never names a sibling or clarifies how it differs from coda_list_rows, which is the immediately adjacent operation.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as coda_list_docs or coda_list_rows. The agent must infer that this is the step to find table IDs before reading rows.

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