Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id (uuid) returned by subscribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 states the operation is a soft delete ("deactivated (not deleted)"), that historical events remain queryable via recent_alerts, and that ownership is enforced. What it omits is failure behavior — whether calling twice on an already-cancelled id errors or is a no-op, and what an invalid or foreign id returns.

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?

Two compact sentences, each front-loaded with the operative fact: what it does first, then the non-obvious consequence (soft delete + historical retention). No filler, no restatement of the title.

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, this covers nearly everything an agent needs: the soft-delete semantics, retention via recent_alerts, and the ownership gate. Only error and idempotency semantics are missing, which is a modest gap rather than a blocking one.

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 parameter already documents that the uuid comes from subscribe, so the description adds little beyond "by id." Its only extra framing is the ownership constraint on that id, which is useful but is really behavioral rather than syntactic. Baseline 3 applies when the schema does the heavy lifting.

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?

"Cancel a subscription by id" gives a specific verb and resource in the first four words, and the mention of recent_alerts for historical events implicitly separates this destructive-path tool from the read-only listing/alerts siblings. An agent knows exactly what operation this performs 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 Guidelines4/5

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

The description establishes clear applicability: use it with a subscription id obtained from subscribe, and only for subscriptions you own. It does not name an explicit alternative (e.g., pausing versus cancelling, or list_subscriptions to find the id first), so it stops short of full when/when-not routing.

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.