Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id (uuid) returned by subscribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 burden and does well: it discloses the authorization model (ownership enforced, own subscriptions only) and the critical soft-delete behavior (row deactivated, not deleted; historical events still available). It omits idempotency and error behavior for an already-cancelled or non-existent id, which keeps it from a 5.

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?

Three short sentences, front-loaded with the action, then the authorization constraint, then the consequence. Every sentence carries distinct information and none is 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 one-parameter mutation with no annotations and no output schema, the description covers the essentials an agent needs: what it destroys, who may do it, and how to recover the data afterwards. Only the response shape and failure modes for invalid ids 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?

Schema coverage is 100% and the single 'id' parameter is already documented as a uuid returned by subscribe, so the schema does the work. The description restates that the id identifies the subscription to cancel but adds no format, sourcing, or validation detail beyond the schema.

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?

States a specific verb and resource ('Cancel a subscription by id') with the ownership scope immediately attached. An agent can tell this apart from list_subscriptions or recent_alerts without opening the schema.

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?

Usage is implied by the verb and by the note that historical events remain reachable via recent_alerts, which hints at the alternative of reading rather than cancelling. However, it never explicitly says when to prefer this over list_subscriptions or how to obtain the id in the first place beyond the schema's reference to subscribe.

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.