Skip to main content
Glama

Oviond

by com.oviond.api
OverviewDiscussionsAdmin

Delete connected datasource

delete_connection
Destructive

Delete a datasource connection — every widget pulling data from it will break

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYesConnection ID to delete (from connected_datasources)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoConfirmation that the connection was deleted. It is unlinked from every client that used it, and their widgets fall back to demo data.
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / connection_id
      Added value: +{
+  "description": "Connection ID to delete (from connected_datasources)",
+  "type": "string"
+}
    • removedInput schema / properties / id
      Removed value: -{
-  "description": "Datasource connection ID to delete (from connected_datasources)",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "id"
-]New value: +[
+  "connection_id"
+]
    • 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. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Confirmation that the connection was deleted. It is unlinked from every client that used it, and their widgets fall back to demo data."
+    },
+    "success": {
+      "description": "True when the call succeeded. A failure comes back as an error result instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already include destructiveHint=true, but the description adds concrete impact information: 'every widget pulling data from it will break'. This goes beyond the generic destructive flag by telling the agent exactly what downstream effect to expect.

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?

A single, well-structured sentence conveys the action and its most important consequence without wasted words. The key behavioral warning is front-loaded.

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

Completeness5/5

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

For a one-parameter destructive tool with annotations and an output schema, the description covers everything needed: what to delete, where to get the ID, and what impact to expect. Nothing critical is missing.

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 only parameter connection_id already includes a useful origin hint ('from connected_datasources'). The description does not need to add more parameter detail; baseline 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 states the specific action ('delete a datasource connection') and the resource affected, and immediately clarifies the consequence. This clearly distinguishes it from related operations like unlink_datasource or rename_connection.

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

Usage Guidelines3/5

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

The description implies use when one wants to permanently remove a datasource connection and accept that dependent widgets will break. It does not explicitly contrast with sibling tools like unlink_datasource, leaving the choice to inference.

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