Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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 behavioral disclosure. It does state the response fields and implies a safe read, and the active/inactive distinction is meaningful context. However, it says nothing about authentication scope, pagination or result limits, or ordering, which matter for a list operation that could return many rows.

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 sentences, both load-bearing: the first states scope and return shape, the second routes the agent to the right moments for use. Nothing is repeated from the schema and the purpose is front-loaded.

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-optional-parameter read tool with no output schema, listing the returned fields compensates well for the missing output schema, and the usage sentence orients the agent. Only edge behavior such as result size or ordering is left 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 description coverage is 100%, and the single optional parameter include_inactive is fully documented in the schema with its default. The description adds no further meaning to it, so the baseline of 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?

"List the caller's active subscriptions" gives a specific verb, resource, and scope (the caller's own, active only), and the next sentence enumerates exactly what is returned. It does not explicitly contrast with any other tool, but among a family of identically named subscription listers the domain namespace in the tool name does that work.

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 names two concrete situations: reviewing what you're monitoring before adding more, and finding an id to cancel. That is clear positive guidance. There is no when-not condition and no sibling tool is named, so the agent must infer which tool performs the add or cancel step.

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.