Skip to main content
Glama

onboarding_support

Read-only

The paid 1:1 onboarding offer and included support. Call with no args for every published offer, or with a country. Published hourly onboarding exists for India (₹5,000 / 10 hours) and the US ($300 / 10 hours) only — for any other country the response sets hasHourlyOffer:false and you must NOT invent or convert one. Also returns the always-included basic support and the SEPARATE done-for-you migration service note per country. Read-only public data.

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

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code. Omit to return every published offer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already supply readOnlyHint=true and openWorldHint=false, so "Read-only public data" adds nothing new. Beyond that baseline, the description discloses the response shape (hasHourlyOffer:false for unlisted countries, inclusion of basic support and the migration note), which is valuable given there is no output schema, and it explicitly forbids fabricating an offer — behavior no annotation captures.

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 sentences, front-loaded with what the tool returns, then the invocation modes, then the hard constraint. There is no filler or restated boilerplate; even the pricing details are load-bearing because they define what counts as a published offer.

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

Completeness4/5

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

For a single optional parameter tool with no output schema, the description covers the return payload's key fields and the critical edge case (unlisted country). It stops short of enumerating the full response structure, but with no output schema and a simple enum-constrained input, an agent has enough to call it correctly and interpret the result.

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 coverage is 100% and the enum already enumerates all valid codes, so the baseline would be 3. The description earns more by explaining the semantic consequence of the parameter: only India (₹5,000 / 10 hours) and the US ($300 / 10 hours) have published hourly onboarding, and all other enum values yield hasHourlyOffer:false. That is meaning the schema itself cannot convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies both the resource (the paid 1:1 onboarding offer plus bundled basic support) and an adjacent artifact (the separate done-for-you migration service note). It is clear what data is returned, though it never names the sibling `country_support`, so an agent still has to infer which of the two country-oriented tools to pick.

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 concrete invocation branches: call with no args for every published offer, call with a `country` for one. It also states a strong exclusion — do not invent or convert an hourly offer for countries other than IN/US — which is exactly the kind of guidance that prevents misuse. What is missing is any pointer to an alternative tool.

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