Skip to main content
Glama
Sign In
OceanBase Oracle MCP Server

OceanBase Oracle MCP Server

by EwanJasper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

confirm_write

Confirm and execute a write operation using a token from preview_write. Token is valid for single use and expires immediately after.

Instructions

【两阶段确认 - 第二步】确认并执行写操作。需要传入 preview_write 返回的 token。执行后 token 立即失效，不可重复使用。

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": {
      "token": "<token>"
    },
    "name": "confirm_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYespreview_write 返回的一次性确认令牌

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses that the token becomes invalid after use and cannot be reused. However, does not detail what the write operation entails or potential side effects. Given no annotations, this is reasonable.

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?

Two sentences, front-loaded with purpose, no fluff. Every sentence is meaningful and concise.

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?

Given simple single-parameter tool with no output schema, description covers workflow step and token behavior. Could mention expected outcome (e.g., success/failure), but overall sufficient.

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 the schema already describes token as a one-time token from preview_write. The description adds workflow context but does not add significant new 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?

Description clearly states it is the second step of a two-phase confirmation, confirming and executing a write operation. It specifies the required input (token from preview_write) and distinguishes itself from sibling tools like preview_write.

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 when to use (after preview_write) and that the token is one-time use. Does not explicitly mention when not to use, but the two-step process context is clear enough.

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