Skip to main content
Glama

ADV IT Performance (AEO websites)

Query ADV Service Catalog & Pricing

query_service_offer
Read-onlyIdempotent

Query machine-readable pricing, deliverables, turnaround SLA, and checkout endpoints for ADV Strategy Pro packages ($197 Action Plan, $697 Landing Page, $2,497 AEO Website, $4,997 Multi-Service Growth Website).

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

Input Schema

NameRequiredDescriptionDefault
tierNoProduct tier or SKU: 'ENTRY' ($197), 'CORE' ($697), 'PRO' ($2,497), 'PREMIUM' ($4,997), 'ALL'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful return content categories such as deliverables, turnaround SLA, and checkout endpoints, but it does not disclose response shape, pagination, or default behavior when the optional tier is omitted.

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 description is a single front-loaded sentence with no filler and quickly establishes the queryable content. The parenthetical price list is somewhat redundant with the schema's tier values, but it does not obscure the request.

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

Completeness3/5

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

For a simple read-only catalog query with strong annotations, the description covers the main returned data categories at a high level. However, with no output schema and an optional tier parameter, it should clarify default tier/ALL behavior and return shape, and it does not explicitly distinguish itself from sibling tools.

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 tier parameter is fully documented with values and prices in the input schema. The description repeats package prices but adds no syntax, defaults, or selection semantics beyond what the schema already provides.

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 uses a specific verb and resource ('Query' + pricing/deliverables/SLA/checkout endpoints for ADV packages), making the purpose clear. It does not explicitly differentiate the tool from sibling names, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named for overlapping catalog or offer lookups. The only usage signal is the implied context of retrieving package pricing and service details.

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