Skip to main content
Glama
Sign In
Hellio Messaging MCP server

Hellio Messaging MCP server

Official
by HellioSolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Switch an app between test and live

hellio_ussd_switch_app_mode

Switch a USSD app to test or live mode. Going live requires an active purchased extension.

Instructions

Switches the app to test (sandbox) or live. Going live requires an active purchased extension for the app, otherwise the call returns 402 extension_required. Requires the ussd scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "mode": "<mode>"
    },
    "name": "hellio_ussd_switch_app_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe app id.
modeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate mutating (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it requires the 'ussd' scope and can return a 402 error if extension missing, providing useful behavioral context beyond annotations.

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 concise sentences, front-loaded with purpose and followed by key condition. No filler or redundancy.

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

Completeness3/5

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

Description covers purpose, precondition, and error case, but lacks mention of successful return value or how to verify the switch. Without output schema, this gap reduces completeness.

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 50% (id described, mode not). Description mentions mode values ('test'/'live') but adds little extra beyond the enum; id is not elaborated. Baseline 3 due to moderate coverage, and description partially compensates for mode.

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 tool switches an app between 'test' and 'live' modes, with the specific verb 'Switches' and resource 'app'. It distinguishes from sibling tools (e.g., create, delete) by focusing on mode change.

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?

The description provides context on when to use (switching mode) and a precondition for 'live' mode (requires active extension). It implies when not to use (if no extension for live), but does not explicitly state alternatives.

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

Deploy Server

Other Tools