Skip to main content
Glama

oviond

by com.oviond
OverviewDiscussionsAdmin

Update custom dataset

update_custom_data

Update a custom-data dataset — send only the fields you want to change (e.g. { raw_data, columns }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustom-data ID (from list_custom_data)
nameNoDataset name
columnsNoReplacement column definitions — send alongside raw_data when the shape changed
raw_dataNoReplacement rows, each an object keyed by column name — replaces every stored row
file_nameNoOriginal file name
file_sizeNoFile size in bytes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe dataset as saved — id, name, file_name and columns.
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / properties / success / description
      Previous value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false (not read-only) and destructiveHint=false. The description adds the key behavior that only provided fields are updated, implying others remain unchanged. This is useful beyond annotations, but it doesn't disclose other behaviors like whether raw_data fully replaces stored rows (already in schema) or any side effects.

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, front-loaded sentence that states the purpose and the key usage behavior (partial update). No wasted words, and the example is concise. It is efficient and easy to parse.

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?

The tool has 6 parameters, but the schema covers all with descriptions. The description adds the essential partial-update behavior. It doesn't mention output, but an output schema exists (per context) so that is covered. Missing is any guidance on when to use this over similar update tools, but the core update semantics are well conveyed. Overall, it is adequate for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 6 parameters, so baseline is 3. The description adds the partial-update semantics ('send only the fields you want to change') which is not captured in the schema. It gives an example with raw_data and columns, clarifying that these are the commonly changed fields. This adds meaningful value beyond 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 description states the verb 'update' and the resource 'custom-data dataset', which is clear. It also specifies partial update behavior. However, it does not explicitly distinguish from sibling update_custom_data_widget, though the resource is different. The distinction is implied by the resource name but not stated.

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 gives guidance on how to perform the update (send only changed fields) but provides no guidance on when to use this tool versus alternatives like update_custom_data_widget or create_custom_data. No mention of prerequisites or conditions for selecting this tool.

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

All oviond toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources