Skip to main content
Glama

Current Horizon support policies

get_support_policy
Read-only

Answers activation and first-use timing, refund eligibility, hotspot and speed policy, or human support availability from Horizon's shared policy constants. No order ID or verification is needed. This never performs a refund or a handoff.

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": {
      "topic": "<topic>"
    },
    "name": "get_support_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Output Schema

NameRequiredDescriptionDefault
urlYes
topicYes
nextStepYes
statementYes
humanSupportUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds real value beyond that by stating no order ID or verification is required and by explicitly capping the tool's authority (no refunds, no handoffs). It does not say whether answers are cached/static or how current the constants are, but the boundaries an agent could otherwise over-assume are made explicit.

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, each doing distinct work: scope, prerequisites, and limits. The capability statement is front-loaded and nothing is repeated from the title or annotations.

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?

The tool is a single-enum read with an output schema, so return values need no explanation. The description covers scope, the four accepted topics, absence of required identifiers, and hard behavioral limits — everything an agent needs to call it correctly and to not expect a refund action.

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?

Schema description coverage is 0%, but the description compensates by expanding each enum value into the actual question it answers (activation = first-use timing, refunds = eligibility, hotspot_and_speed = policy, support = human availability). That is genuine added meaning over the bare enum strings, though it never states that these four phrases correspond to the accepted topic values, leaving the mapping for the agent to infer.

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?

Uses a specific verb (answers) with a precisely enumerated set of question domains — activation timing, refund eligibility, hotspot/speed policy, human support availability — that map one-to-one onto the enum. It also states the source of the answers (Horizon's shared policy constants), so an agent can tell this apart from action-oriented siblings like check_device_compatibility or list_destination_plans.

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?

Gives clear triggering conditions (policy/timing/eligibility questions) and two explicit exclusions: it never performs a refund or a handoff, and it requires no order ID or verification. It does not name a sibling to use for refund execution or escalation, so the 'instead, use X' half of the guidance is left implicit.

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