Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Remove a notification channel

notify_remove_channel
DestructiveIdempotent

Delete a saved channel. 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": "notify_remove_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA short name for the channel, e.g. "sales-alerts" (lowercase letters, numbers, dashes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/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 known without the description. The description adds no context beyond restating the delete -- it doesn't say what happens to existing subscriptions or delivery history, or whether removal is recoverable. "Free." is unexplained (cost? plan tier?) and doesn't compensate.

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?

Front-loaded and very short, but "Free." is an orphan fragment whose meaning is unclear, so not every sentence earns its place.

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?

For a destructive mutation with no output schema, the definition leaves key questions unanswered: what happens to channels still referenced by events or routing, and whether the operation can be undone. Annotations cover the destructive flag but not the consequences.

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% and the single `name` parameter is fully documented in the schema with a pattern example. The description adds no further semantics about the name, so baseline 3 applies.

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?

"Delete a saved channel" states a specific verb and resource, and the notify_* sibling naming (add_channel, list_channels) makes the target unambiguous. It does not explicitly contrast with those siblings, and the trailing "Free." adds nothing to purpose.

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?

No indication of when to remove a channel versus when to keep it, no prerequisites, and no mention of the alternative (e.g., notify_subscribe/unsubscribe if the goal is only to stop receiving alerts). The agent must infer everything.

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