Skip to main content
Glama

Global Shopaholics services, plans, fees and payment methods

get_services_and_fees
Read-onlyIdempotent

Global Shopaholics' services (US address, consolidation, Assisted Purchase, shipping), subscription plans (Basic free, Premium $9.99/mo, Business $14.99/mo) and published fees (incl. Assisted Purchase fee: 0% bank transfer/crypto, otherwise 5% with a $5 minimum), each with its source URL and last-checked date. Use when a user asks what GS costs, how to pay, or what services exist.

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_services_and_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoNarrow the answer.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 this a read-only, idempotent, non-destructive, closed-world lookup, so the safety profile is covered. The description adds genuinely new behavioral context: every fact is returned with a source URL and last-checked date, which tells the agent the data is curated and dated rather than live. It stops short of saying how fresh or how often refreshed, which would have completed the picture.

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 content inventory is front-loaded in one dense sentence and the usage trigger follows, so the agent hits the purpose first. The embedded pricing detail (0% vs 5% with $5 minimum) is arguably more than needed for tool selection, but it is real payload the user is likely to ask about and does not obscure the purpose.

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?

With one optional enum parameter, no output schema and no nested objects, the description carries everything an agent needs: what is returned, that provenance accompanies each item, and when to reach for it. Nothing essential to invoking it correctly 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 description coverage is 100% and the single topic parameter has a documented enum, so the schema already carries the semantics. The description implicitly maps its content categories (services, plans, fees, payment) onto those enum values but adds no narrowing syntax or default behavior beyond what the schema 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?

The description names a specific verb-and-resource pairing (returns services, subscription plans, published fees and payment methods) and enumerates the exact contents, including price points and the Assisted Purchase fee rule. An agent knows precisely what this tool answers without opening the schema.

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?

It gives an explicit trigger: 'Use when a user asks what GS costs, how to pay, or what services exist.' That covers the primary intents clearly, but it names no exclusions or alternatives — siblings such as get_shipping_rates and estimate_landed_cost handle computed shipping/landed costs, and the description does not route the agent away from this tool for those.

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.