Skip to main content
Glama

Check database progress

databaseReconcile
Idempotent

Check progress on this app’s managed database creation or recovery — Check progress on the dashboard’s Database page. Safe to repeat, and it never creates a second database: Tofu searches only for the attempt it already recorded. An interrupted or failed creation attempt is reconciled against the provider, and the result reports its state. For a restore whose Storage files are still going back (restore.outcome in_progress), the answer carries the restore’s report as it stands (restore), and Tofu puts the files back on its own every few minutes, so a repeated call only reads that report again; the app is reconnected once the last file is back and checked, and restore then reads restored. It returns no credential and cannot run SQL or migrations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "databaseReconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
refYes
exitYes
stateYes
regionYes
schemaYes
archiveYes
enabledYes
messageYes
restoreNo
providerYes
nextStepsYes
inactivityNo
agentPromptYes
lifecycleModeNo
storedArchiveNo
environmentKeysYes
lifecycleFailureYes
requiresDeploymentYes
manualRetentionSinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare idempotentHint=true and destructiveHint=false, consistent with 'safe to repeat' and 'never creates a second database' — so the description is largely restating them, though it usefully adds that reconciliation happens against the provider. It adds genuinely new limits: no credential is returned and it cannot run SQL or migrations, which scopes the tool beyond its annotations. The readOnlyHint=false is not explained, but the provider-reconciliation clause implicitly accounts for the non-read-only nature.

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?

The primary purpose and the safety claim are front-loaded in the first sentence, and each subsequent sentence adds distinct information (non-duplication, reconciliation, restore polling states, capability limits). It is dense with parenthetical field references and backticked identifiers, which is efficient for an agent but borders on overlong.

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?

An output schema exists, so return values need not be spelled out, yet the description still explains the 'restore' report and its 'in_progress'/'restored' outcome states, which is helpful for polling logic. Combined with the non-duplication and no-credential guarantees, it covers what an agent needs for this low-parameter tool; only the projectId argument is left 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?

There is one parameter, projectId, and schema description coverage is 0%, so the description carries the burden — yet it never mentions the parameter at all. The field name is self-explanatory as a UUID identifier, which keeps this from being a gap that blocks correct invocation, but no meaning is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause states a specific verb and resource: 'Check progress on this app's managed database creation or recovery.' It also rules out the most likely confusion with its sibling databaseCreate by asserting 'it never creates a second database.' It stops short of distinguishing itself from databaseStatus, leaving some ambiguity among the progress-reporting siblings.

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?

Clear context for when to call: it polls an existing creation or recovery attempt, is safe to repeat, and during a restore returns the current report until 'restore' reads 'restored'. It gives no explicit when-not or named-alternative guidance (e.g. databaseStatus), so an agent still has to infer which sibling reports what.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources