Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda List Controls

coda_list_controls
Read-onlyIdempotent

List all controls in a Coda doc, returning names, IDs, types, and current values so you can inspect interactive page elements.

Instructions

List all controls (sliders, select lists, date pickers, etc.) in a Coda doc.

Returns control metadata including name, ID, type, and current value. Controls are interactive UI elements on pages. Use coda_get_control to read a specific control's current value.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of controls to return (1-200)
cursorNoPagination cursor from a previous response
doc_idYesThe doc ID to list controls from

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.4/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 genuine context by enumerating what the operation actually returns (name, ID, type, current value) and clarifying that controls are interactive UI elements on pages. It does not discuss pagination behavior, but the schema carries that.

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, zero filler, with the scope statement front-loaded and the return contents and alternative tool following in priority order. Nothing is wasted and nothing important is buried.

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 usefully compensates by summarizing the returned fields. Parameter behavior is fully covered by the 100%-coverage schema. The only minor gap is that pagination sequencing (limit/cursor usage across calls) is never mentioned, but the schema defaults make this inferable.

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% and all three parameters (doc_id, limit, cursor) are documented in the schema itself. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 and resource ('List all controls ... in a Coda doc') and immediately disambiguates the resource with concrete examples (sliders, select lists, date pickers). An agent can distinguish this from coda_get_control 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 Guidelines5/5

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

Explicitly names the alternative tool and the condition that selects it: 'Use coda_get_control to read a specific control's current value,' which implies this tool is for enumerating controls rather than reading one. That is a clear when-to-use/when-to-use-the-other routing statement.

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