Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Get Row

coda_get_row
Read-onlyIdempotent

Retrieve a single row from a Coda table by row ID or display column value, returning all column values. Use when you need one specific row; query multiple rows with coda_list_rows instead.

Instructions

Get a single row from a Coda table by ID or display column value.

Returns all column values for the specified row. Use this when you have a specific row ID or know the display column value. For querying multiple rows with filters, use coda_list_rows instead.

Input Schema

NameRequiredDescriptionDefault
doc_idYesThe doc ID containing the table
row_id_or_nameYesRow ID or name (display column value)
table_id_or_nameYesTable ID or name
use_column_namesNoUse column names (True) or IDs (False) in row values

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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful behavioral context by stating that it returns all column values for the specified row, though it does not mention error behavior (e.g., row not found) or permission scope.

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?

Three short sentences, front-loaded with purpose and return behavior, then usage constraint and alternative. Every sentence earns its place with no redundant or vague filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-row read tool with rich annotations and complete schema coverage, the description supplies the needed scope, alternative routing, and return summary. Although no output schema exists, it states that all column values are returned, which is sufficient for correct invocation.

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%, so the schema already documents all four parameters including row_id_or_name and use_column_names. The description adds the ID/display-column-value distinction, but that is essentially repeated from the schema and it says nothing about use_column_names.

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?

States a specific verb (Get) and resource (single row from a Coda table), including the accepted lookup keys (row ID or display column value). It explicitly distinguishes itself from coda_list_rows, so an agent can route correctly without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it (when you have a specific row ID or know the display column value) and names the alternative for multi-row filtering (coda_list_rows). This gives clear when-to-use and when-not-to-use guidance.

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