Skip to main content
Glama

quantum_subscribe

DISABLED: webhook subscriptions are switched off (no registration, no delivery). Poll quantum_feed for OracleNet events.

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": "quantum_subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
didNoYour DID (optional)
actionNoregister, unregister, or list
eventsNoComma-separated event types or 'all'
webhook_idNoFor unregister: webhook ID
webhook_urlNoURL where we POST events. Required when action=register.

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 burden and discharges the most important trait: the tool is disabled, so nothing is registered and no events are delivered. It stops short of saying what actually happens if an agent calls it anyway — hard error, empty result, or silent no-op — which matters for an agent that has already selected the tool.

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, front-loaded with the 'DISABLED' marker so an agent scanning the first token already knows the disposition. Every clause earns its place: the shutdown scope and the redirect each do distinct work.

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 five-parameter mutation tool with no annotations and no output schema, the definition supplies the one fact that dominates everything else — the tool is off — plus a working fallback. The gap is the call-time behavior of a disabled endpoint and any note that the schema's register/unregister/list paths are inert, which would prevent a plausible misread of the still-populated schema.

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%, so every one of the five parameters (did, action, events, webhook_id, webhook_url) is already documented in the schema, including the required-when-register note on webhook_url. The description adds no parameter meaning and effectively renders the parameters moot without saying so explicitly; 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 identifies the resource (webhook subscriptions) and its operations in negative form — 'no registration, no delivery' — which, combined with the action enum, makes the tool's intended purpose inferable. It distinguishes itself clearly from quantum_feed by pointing there for the live alternative, though it never states the positive verb+resource in one clean clause.

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

Usage Guidelines5/5

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

It gives an unambiguous directive: this tool is off, do not use it, and poll quantum_feed for OracleNet events instead. A named alternative plus an explicit condition is exactly the when-to-use/when-not-to-use pattern, even though the alternative is a sibling the agent must locate itself.

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.

Resources