Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Resolve Browser Link

coda_resolve_browser_link
Read-onlyIdempotent

Resolve a Coda browser URL into API-compatible IDs for the doc, page, table, row, or column it points to. Use this first when a user supplies a Coda link instead of IDs.

Instructions

Resolve a Coda browser URL to API resource IDs.

Converts a browser URL (e.g. from the address bar or a shared link) into API-compatible IDs for the doc, page, table, row, or column it points to. Use this as the first step when a user provides a Coda URL instead of IDs. Returns a type field indicating the resource kind and corresponding IDs.

Input Schema

NameRequiredDescriptionDefault
urlYesA Coda browser URL to resolve (e.g. https://coda.io/d/...)

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?

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and repeatability are covered. The description adds value beyond them by disclosing the return shape (a type field plus resolved IDs) and the breadth of resource kinds handled. It omits error behavior for malformed URLs, so not a 5.

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?

Front-loaded with the core action, then purpose, then usage, then return value; each sentence pulls weight. Slightly verbose with the parenthetical example, but nothing is wasted.

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 single-parameter read tool with no output schema, the description covers what it does, when to use it, and what it returns (type field and IDs). An agent has everything needed to invoke it correctly.

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% for the single url parameter, so the baseline is 3. The description marginally extends the schema by noting the URL can come from the address bar or a shared link, but adds no format or constraint details beyond that.

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 (Resolve) and resource (Coda browser URL to API resource IDs), and the scope is concrete: server, doc, page, table, row, or column. An agent can distinguish this from siblings like coda_get_doc, which take IDs rather than URLs.

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 the triggering condition: 'Use this as the first step when a user provides a Coda URL instead of IDs.' This clearly positions it relative to every ID-consuming sibling. It does not spell out exclusions or failure cases (e.g. invalid/non-Coda URLs), keeping it just below a 5.

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