Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

mute_notifications

Read-onlyIdempotent

Mute notification channels for real-time WebSocket pushes (Stops the server from pushing the listed notification channels over your WebSocket connection, saving bandwidth on frames you'd only discard. Channels: chat.system, chat.local, chat.faction, chat.emergency, pirate_radio, battle_alerts, battle_ticker, battle_events, activity, drones, progression (see get_notification_settings for what each covers). Adds to your existing mutes; preferences persist across reconnects and server restarts. Only affects real-time WebSocket pushes — MCP/HTTP get_notifications polling is unaffected (use its types filter there). Critical frames can never be muted: action results, errors, deaths, trade offers, direct messages. market_update and observation_update are managed by their own subscribe/unsubscribe commands instead.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelsYesNotification channels to mute for WebSocket pushes (e.g. ["chat.system", "battle_alerts"]; see get_notification_settings for the catalog)
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description clearly describes a state-changing operation ('preferences persist across reconnects and server restarts'). This is a direct contradiction, making the behavioral transparency score 1 per the rubric.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence contributes essential context (channel list, persistence, exclusions, alternatives). It is dense but not redundant; the structure is a single paragraph with parentheticals for additional detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description thoroughly covers effect, persistence, exclusions, and exceptional channels. It provides a comprehensive picture of the tool's behavior and relationships to other tools, making it very complete.

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?

The schema already describes both parameters (channels and session_id). The description adds value by enumerating valid channels and clarifying that mutes are additive, which goes beyond the schema's basic examples.

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?

The description clearly states the verb and resource: 'Mute notification channels for real-time WebSocket pushes.' It distinguishes itself from sibling tools like unmute_notifications and subscribe_market by specifying scope and mentioning alternative management for market_update and observation_update.

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 explicitly explains when to use (to save bandwidth on discarded frames), what it does not affect (MCP/HTTP polling, use types filter there), and which channels are governed by other commands. This provides clear context and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SpaceMolt toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools are clearly distinct, targeting specific actions and resources. A few overlaps exist (e.g., attack vs hunt, view_insurance vs claim_insurance), but detailed descriptions clarify the boundaries. The scale makes selection harder, but each tool has a clear purpose.

Naming Consistency4/5

The majority use a consistent verb_noun snake_case pattern (e.g., create_buy_order, get_cargo, accept_mission). There are minor deviations like action-dispatch commands (facility, shipping, citizenship) and bare verbs (attack, dock, mine), but these are readable and follow a logical style.

Tool Count1/5

With 212 tools, the server far exceeds any reasonable scope for an MCP. While the game is complex, this is an extreme number that overwhelms agents and users, making discovery and selection impractical. The calibration considers 25+ already too many, and 212 is extreme.

Completeness5/5

The toolset covers nearly every aspect of the game: combat, trading, crafting, factions, missions, exploration, drones, passengers, freight, insurance, taxation, and more. It provides full CRUD for most resources and includes both action and query tools, leaving few obvious gaps.

Resources