Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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 at all, the description carries the full burden and does so well: it discloses the soft-delete semantics (row deactivated, not deleted), the authorization model (ownership enforced), and the downstream consequence (history retrievable via recent_alerts). It omits idempotency/error behavior when the id is unknown or not owned, and gives no sense of the response.

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, nothing repeated, and the core action is front-loaded ahead of the side-effect detail. Every sentence contributes new information (action, authorization, data-retention consequence).

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 action, permission model, and post-cancellation data availability — the things an agent most needs before invoking it. Missing only failure-mode and return-value context, which is a modest gap given the tool's simplicity.

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?

Only one parameter, and the schema already documents it at 100% coverage ('Subscription id (uuid) returned by subscribe'). The description's 'by id' adds nothing beyond the schema, so the 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?

The description names a specific verb and resource ('Cancel a subscription') plus the selector ('by id'), so the agent can tell it apart from listing or read tools in the sibling set. It stops short of explicitly routing to a sibling (e.g. list_subscriptions for finding ids), which keeps it from a 5.

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

Usage Guidelines4/5

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

It states a concrete precondition — ownership is enforced, only your own subscriptions can be cancelled — and points the agent to recent_alerts for the historical events that remain after cancellation. It gives no explicit when-not guidance or pointer to list_subscriptions for discovering the id, so exclusions are missing.

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.