Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Delete a saved dashboard

view_delete
DestructiveIdempotent

Delete a saved view; links to it stop working. Free.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe saved view's name, like weekly-sales.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuine consequence context beyond annotations: 'links to it stop working' tells the agent that external links are broken as a side effect, which is meaningful destructive behavior disclosure.

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

Conciseness4/5

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

Very terse and front-loaded with the action and consequence. 'Free' is slightly cryptic (cost/model credit?), but the sentences are efficiently packed with no filler.

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?

For a single-parameter delete tool whose annotations fully cover the safety profile and whose sole parameter is fully schema-documented, this is nearly complete. The consequence of deletion is stated; only permission/ownership requirements are unaddressed.

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?

The single 'name' parameter is fully documented in the schema (100% coverage) including an example format ('weekly-sales'). The description adds nothing about the parameter, so per the high-coverage baseline a 3 is appropriate.

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?

Specific verb+resource ('Delete a saved view') that cleanly separates it from siblings like view_get, view_save, view_list, and view_show. It does not explicitly name a sibling, but no sibling performs deletion, so disambiguation is unambiguous.

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 exclusion of alternatives, and no prerequisites (e.g., ownership or permissions). 'Delete a saved view' implies the action but leaves all routing and preconditions to inference.

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

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