Skip to main content
Glama

ADV IT Performance (AEO websites)

List ADV Strategy Pro Offers & Prices

get_offers
Read-onlyIdempotent

Return the current ADV Strategy Pro service tiers with USD prices, billing type and the approved next step for each. Request a tier for full scope and action label. Read-only; sourced from the canonical commerce catalog.

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

Input Schema

NameRequiredDescriptionDefault
tierNoOptional tier id. Omit for a compact list of all tiers; pass an id for that tier's full scope and description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low; the description still adds provenance ('sourced from the canonical commerce catalog') and enumerates what comes back (prices, billing type, approved next step). It does not discuss caching, currency conversion, or how stale catalog data might be, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the returned data and followed by the parameter behavior. 'Read-only' restates the readOnlyHint annotation and is the only mildly redundant wording.

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?

There is no output schema, so the description must carry return semantics, and it does so by naming prices, billing type and the approved next step per tier. With one optional, fully documented parameter, nothing essential for a correct call is missing; only the tier-response wording inconsistency slightly undercuts it.

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%, so a baseline of 3 is warranted, but the description adds meaning by framing the tier as the switch between a compact list and 'full scope and action label'. Note a slight mismatch: the schema says passing a tier returns 'full scope and description' while the description promises 'full scope and action label'.

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 names a specific verb and resource: returning ADV Strategy Pro service tiers with USD prices, billing type and approved next step. The branded scope ('ADV Strategy Pro') makes it distinguishable from the generic sibling query_service_offer, but it never explicitly contrasts itself with that or any other sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is only implicit at the parameter level: 'Request a tier for full scope and action label' tells the agent what passing a tier buys, and the schema clarifies omitting it yields a compact list. There is no statement of when to choose this over query_service_offer or get_adv_knowledge.

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