Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Get Formula

coda_get_formula
Read-onlyIdempotent

Retrieve the current value, type, and error status of a named formula in a Coda doc. Use it to check computed formula results in real time.

Instructions

Get the current value of a named formula in a Coda doc.

Returns the formula's name, ID, type, current value, and whether it has an error. The value is computed by Coda and reflects the latest state. Use coda_list_formulas to discover available formulas in a doc.

Input Schema

NameRequiredDescriptionDefault
doc_idYesThe doc ID containing the formula
formula_id_or_nameYesFormula 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.1/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 genuinely useful context beyond that: the return fields (name, ID, type, current value, error state) and the note that the value is computed by Coda and reflects the latest state, which explains the openWorld/live-computation behavior.

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?

Three short sentences, front-loaded with the core action, followed by return-value context and the sibling pointer. Efficient with no filler, though the second sentence is slightly enumerative.

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?

With no output schema, the description usefully enumerates the returned fields, compensating for that gap. It is complete for a simple two-parameter read tool; only minor details like error semantics or permission requirements are 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 coverage is 100%, with both doc_id and formula_id_or_name documented in the schema, so the schema carries the burden. The description only indirectly reinforces that formula_id_or_name accepts a name ('named formula') and adds no format or lookup semantics beyond the schema.

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 ('the current value of a named formula in a Coda doc'), and distinguishes itself from the sibling coda_list_formulas by describing what it retrieves versus what it enumerates. An agent can tell it apart from other coda_get_* tools 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 routes the agent: 'Use coda_list_formulas to discover available formulas in a doc,' which clarifies the discovery-vs-fetch workflow. It gives clear context for use but states no exclusions or preconditions (e.g., permissions needed to read formulas).

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