Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__list_subscriptions

List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nj-mvc__list_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_inactiveNoInclude cancelled subscriptions in the response (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the default 'active' filter and enumerates the returned fields (id, type, params, created_at, last_fired_at, fire_count). It omits pagination or result-size behavior, which matters for a list tool, but a read-only listing has a limited safety profile to disclose.

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 and scope, then return shape, then usage. No filler and nothing buried.

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 read-only list with no output schema, the description covers purpose, return fields, and use cases adequately. The only real gap is any indication of result volume or pagination, which an agent managing large subscription sets would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is fully documented there, so baseline would be 3. The description's emphasis on 'active subscriptions' adds context for what the include_inactive toggle reverts, though it never mentions the parameter by name.

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 ('List the caller's active subscriptions') and immediately scopes it to the caller, so the agent knows it is a personal, not global, listing. The return-field enumeration reinforces exactly what kind of object is returned.

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?

Gives two concrete situations to use it: reviewing what you monitor before adding more, and finding an id to cancel. It does not name the add/cancel tools explicitly, but the intent-to-alternative mapping is clear enough for selection.

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.