Skip to main content
Glama

NS Pros MCP Gateway

nobel__unsubscribe

Cancel a subscription by id. Ownership is enforced, you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

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

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id (uuid) returned by subscribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it reveals that ownership is enforced server-side, that the record is soft-deactivated rather than deleted, and that historical events remain reachable through recent_alerts. It stops short of stating idempotency, reversibility, or the failure mode for a nonexistent or already-cancelled id.

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?

Three short sentences, front-loaded with the action and followed by the two facts an agent most needs (ownership and soft-delete). Nothing is redundant, though the retention clause could be folded into the soft-delete sentence for tighter flow.

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 mutation with no annotations and no output schema, the description covers the important behavioral risks: authorization scope, that data is not destroyed, and where the history remains visible. Only error and return behavior for an invalid or already-inactive id is left unstated.

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?

There is a single parameter and schema coverage is 100%, with the schema already explaining that the id is a uuid returned by subscribe. The description adds only the phrase 'by id', so the schema does essentially all the semantic work here, which matches the baseline.

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 names a specific verb (cancel) and resource (subscription) and specifies that the action is keyed on an id. It is unambiguous about what the tool does, though it does not contrast itself with any sibling, since the sibling names belong to other services' namespaces and offer no real alternative within this one.

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 ownership rule ('you can only cancel your own subscriptions') gives an explicit precondition for a successful call, but the description never says when to choose cancellation versus other lifecycle operations or what to do when the id is unknown or already inactive. Usage is implied rather than routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.