Skip to main content
GET

Overview

Parameter defaults are values Danube fills into a tool call when the call leaves them out: Vercel’s teamId, a Sentry organization slug, a DigitalOcean app id. An explicit value in the call always wins. This endpoint returns every defaults row that applies to you on one service, your own rows and your organizations’ rows, plus effective, the merged service-wide result. Precedence, least to most specific:
  1. Organization, whole service
  2. Organization, one tool
  3. You, whole service
  4. You, one tool
Among organizations, the one your request acts as wins. Tool-scoped rows appear in rows but are merged into effective only when their tool matches, so effective here is the service-wide view. The per-tool merge is the defaults field of Describe Tool. Reads are best-effort: when the lookup fails, rows is [] and effective is {}. Auth: Required. API key (danube-api-key header) or JWT.

Path Parameters

string
required
The service UUID or slug. Unknown services return 404.

Response

string
The service UUID, resolved from a slug when one was given
array
Every applicable row. Each has id, user_id (set for your own rows), org_id (set for organization rows), service_id, tool_id (null for a service-wide row), defaults and updated_at.
object
The service-wide rows merged in precedence order, as parameter name to value

Example

The Python and TypeScript SDKs do not wrap this endpoint yet, and there is no MCP tool for reading defaults. describe_tool on MCP shows the effective defaults for one tool.