Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

update-table

Apply JSON Patch operations to update an OpenMetadata table's metadata attributes.

Instructions

Update a table using JSON Patch operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTable UUID to update
operationsYesJSON Patch operations

Implementation Reference

  • The actual handler function for the update-table tool. It asserts write permission, then sends a PATCH request to /tables/{id} with JSON Patch operations.
    export async function updateTable(params: z.infer<typeof updateTableSchema>) {
      assertWriteAllowed();
      return omClient.patch(`/tables/${params.id}`, params.operations);
    }
  • Zod schema for the update-table tool: requires a table UUID (id) and an array of JSON Patch operations.
    export const updateTableSchema = z.object({
      id: z.string().describe("Table UUID to update"),
      operations: z.array(z.record(z.string(), z.any())).describe("JSON Patch operations"),
    });
  • src/index.ts:180-180 (registration)
    Registration of the update-table tool with the McpServer, binding the schema and wrapped handler.
    tool("update-table", "Update a table using JSON Patch operations", updateTableSchema.shape, wrapToolHandler(updateTable));
  • src/index.ts:16-20 (registration)
    Import of updateTableSchema and updateTable from src/tools/tables.ts.
    import {
      listTablesSchema, listTables, getTableSchema, getTable,
      getTableByNameSchema, getTableByName, createTableSchema, createTable,
      updateTableSchema, updateTable, deleteTableSchema, deleteTable,
    } from "./tools/tables.js";
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions JSON Patch but does not disclose behavioral traits like atomicity, failure handling, authorization requirements, or destructiveness. As a mutation tool, more transparency is needed.

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?

The description is a single, concise sentence with no redundant or unnecessary words. It is front-loaded with the key action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool and good schema coverage, the description is minimally adequate. However, it does not mention return value or behavior on failure, and with no output schema, some additional context would be helpful.

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 clear descriptions for both parameters ('Table UUID to update' and 'JSON Patch operations'). The description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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?

The description clearly states the action 'Update' and the resource 'a table', and specifies the method 'using JSON Patch operations'. It effectively distinguishes from sibling tools like 'create-table' and other update tools for different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as when partial updates are needed versus full replacement, or any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/us-all/openmetadata-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server