Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Get Table

coda_get_table
Read-onlyIdempotent

Retrieve metadata for a single Coda table or view, including name, ID, type, row count, parent page, and sort/filter info, without row data or column definitions.

Instructions

Get metadata for a single table or view in a Coda doc.

Returns the table's name, ID, type, row count, parent page, and sort/filter info. Does NOT return row data or column definitions — use coda_list_rows and coda_list_columns for those.

Input Schema

NameRequiredDescriptionDefault
doc_idYesThe doc ID containing the table
table_id_or_nameYesTable ID or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.4.14

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint/idempotentHint annotations covering the safety profile, the description adds genuine value by enumerating what is returned (name, ID, type, row count, parent page, sort/filter info) and what is not. It does not mention auth requirements or pagination, but for a read-only metadata call the disclosure is solid.

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?

Two tight sentences, front-loaded with the core action and followed by the return scope and the exclusion. Every sentence earns its place with no filler.

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 correctly compensates by summarizing the returned fields. Combined with the negative scoping and the read-only annotations, an agent has enough to call it correctly; only auth/pagination behavior is unaddressed.

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 both doc_id and table_id_or_name documented in the schema, so the baseline is 3. The description adds no extra detail on ID vs. name resolution or format, leaving the schema to do all the work.

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?

Names a specific verb and resource ('Get metadata for a single table or view') and scopes it to one entity in a doc. The description also draws a boundary against sibling tools by naming coda_list_rows and coda_list_columns, so an agent can distinguish it without opening the schema.

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 states what the tool does NOT do ('Does NOT return row data or column definitions') and routes the agent to coda_list_rows and coda_list_columns for those cases. It stops short of stating when to prefer this over coda_list_tables for enumerating tables, so it is clear but not fully exhaustive.

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