Skip to main content
Glama
Sign In

GlobalHostia

by com.globalhostia
OverviewDiscussionsAdmin

Get refund, tax and renewal policies

get_policies
Read-onlyIdempotent

GlobalHostia customer policies summarised from the published Terms & Conditions: money-back guarantee, domain and SSL refunds, cancellation, automatic renewal and price changes, billing, taxes and VAT, domain expiry and data retention, with the source link. Use before answering any refund, VAT or renewal question.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOptional filter (default all).

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?

Annotations already declare read-only, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds genuinely new behavior: the content is a summary derived from published Terms & Conditions and includes a source link, warning the agent that this is not the raw legal text.

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?

Two sentences, front-loaded with the resource and its covered topics, then the usage directive. The topic list is long but each item earns its place by telling the agent what questions are answerable. No filler or marketing language.

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?

One optional parameter, rich annotations, no output schema. The description covers purpose, covered subject matter, the usage trigger, and hints at the return payload (source link). Nothing an agent needs before calling it is missing.

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 100% and the single optional `topic` parameter is fully documented in the schema including its enum values and default. The description's topic enumeration loosely mirrors those enum values but adds no new syntax, filtering, or combination semantics beyond what the schema already states.

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?

Names a specific resource (GlobalHostia customer policies) and states exactly what it contains: money-back guarantee, refunds, cancellation, renewal, price changes, billing, taxes/VAT, domain expiry and data retention. The scope is clearly distinguishable from the product, cart, and domain-check siblings.

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 an explicit trigger: "Use before answering any refund, VAT or renewal question." This is actionable and specific about the moment of use. It stops short of naming a when-not condition or an alternative tool, but none of the listed siblings appear to overlap this topic.

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

All GlobalHostia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources