Skip to main content
Glama
Sign In

OneUptime

by com.oneuptime
OverviewDiscussionsAdmin

Create Data Asset

create_data_asset
Destructive

Create a Data Asset. projectId comes from your credentials. Fields: oneuptime_describe_resource.

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": {
      "dataStoreId": "<dataStoreId>",
      "assetKey": "<assetKey>",
      "name": "<name>"
    },
    "name": "create_data_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe table's or view's own name, such as orders.
labelsNo
assetKeyYesThe asset's name with its schema, such as "public.orders": what its metrics and checks name it by.
assetKindNoTable
projectIdNo
schemaNameNo
dataStoreIdYesID of the data store this asset is in.
descriptionNo
freshnessColumnNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description adds little. The only extra context is "projectId comes from your credentials", which hints at auth scoping, but nothing explains what is created, whether duplicates are rejected, or what happens if the referenced data store is wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded with the action, but the fragment "Fields: oneuptime_describe_resource" is ambiguous — it is unclear whether it names a field or tells the agent to call another tool. Space saved comes at the cost of clarity rather than trimming filler.

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

Completeness2/5

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

A nine-parameter, three-required creation tool flagged destructiveHint=true with no output schema needs considerably more than three fragments. An agent cannot predict the returned asset ID or understand required-vs-optional field roles from this description alone.

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 only 33%, and the description covers just one undocumented parameter (projectId, supplied from credentials) and defers the rest to oneuptime_describe_resource. It adds real value for projectId but leaves assetKind, freshnessColumn, schemaName, and labels unexplained beyond the schema's bare types.

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

Purpose3/5

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

"Create a Data Asset" gives a verb and a resource, but it largely restates the tool name and title and never explains what a data asset is or how it differs from create_data_store, create_data_check, or create_data_product. An agent knows it creates something, but not the object's role in the data-observability model.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as update_data_asset or create_data_store. The only routing hint is the cryptic "Fields: oneuptime_describe_resource", which points at a discovery tool rather than explaining when this tool is the right call.

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

All OneUptime 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