Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It discloses the response shape (id, type, params, created_at, last_fired_at, fire_count) and scopes results to the caller, which is useful, but it says nothing about permissions, pagination, ordering, or result volume. The word 'active' also sits slightly at odds with the include_inactive parameter without explaining the default behavior.

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 verb and scope, then the return fields, then the use case. Nothing is redundant and nothing is missing that would need to be said earlier.

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 tool with no output schema, the description covers purpose, return fields, and motivation for calling it, which is close to sufficient. The only shortfall is the absent note on how include_inactive changes the 'active' scope described in the first sentence.

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 include_inactive parameter is already documented in the schema as defaulting to false. The description adds no meaning beyond that and never mentions the parameter, so it neither compensates nor misleads — baseline 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 opens with a specific verb and resource ('List the caller's active subscriptions') and immediately enumerates the returned fields, so an agent knows exactly what the tool retrieves. It does not differentiate from any sibling, though the sibling list here is same-named tools from unrelated domains rather than true alternatives.

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 gives concrete when-to-use conditions: reviewing existing monitors before creating more, and locating an id in order to cancel. It stops short of explicit exclusions or naming a different tool to use instead, so it is clear context rather than a full routing rule.

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.