Skip to main content
Glama

GrowVib: Social Media Growth

get_quote

Read-onlyIdempotent

Get the exact price that will be charged, with no account needed. Call this before every order: never total up the per-1000 prices the catalog tools return yourself, because the quantity bounds and rounding are applied here and nowhere else. Returns unit price and total in USD, priced by the same server-side path a real order uses. It places no order and charges nothing. The result's payment_methods says how the order can be paid: from a connected GrowVib account (connect one over OAuth at the /mcp endpoint, which is where the account ordering tool lives), or, when listed, with no account at all over x402 (USDC on Base or Solana, via create_paid_order or the REST endpoint it names; payment_methods.x402.networks lists the rails).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quantity": "<quantity>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsNoOnly for a subscription option on an auto-delivery service (requires_posts on the option; the quote says when one is missing): how many of the target's future posts to cover. The quantity is then the amount per post and the price is posts times that amount. Omit for every ordinary option.
quantityYesQuantity to order (e.g. number of members or views).
service_idNoThe service: its id or its slug (e.g. telegram-members) from search_catalog or get_service. May be omitted when service_option_id is given, since an option names its service.
service_option_idNoThe plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's Express card is priced (its recommended setup, else its cheapest card that takes the quantity), else the cheapest plain option that fits, and the quote names it. Alone, it also names the service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service_option_id / description
      Previous value: -"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's primary option is priced. Alone, it also names the service."New value: +"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's Express card is priced (its recommended setup, else its cheapest card that takes the quantity), else the cheapest plain option that fits, and the quote names it. Alone, it also names the service."
  2. Changed3 schema fields changed
    • changedInput schema / properties / service_id / description
      Previous value: -"The service id from search_catalog."New value: +"The service: its id or its slug (e.g. telegram-members) from search_catalog or get_service. May be omitted when service_option_id is given, since an option names its service."
    • changedInput schema / properties / service_option_id / description
      Previous value: -"Optional specific service option id; defaults to the service's primary option."New value: +"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's primary option is priced. Alone, it also names the service."
    • changedInput schema / required
      Previous value: -[
      -  "service_id",
      -  "quantity"
      -]New value: +[
      +  "quantity"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / posts
      Added value: +{
      +  "description": "Only for a subscription option on an auto-delivery service (requires_posts on the option; the quote says when one is missing): how many of the target's future posts to cover. The quantity is then the amount per post and the price is posts times that amount. Omit for every ordinary option.",
      +  "type": "number"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing that no order is placed, nothing is charged, pricing uses the same server-side path as a real order, and that no account is required. The payment_methods contract (GrowVib OAuth account vs. x402 USDC on Base/Solana) is genuinely useful behavioral context. Minor gap: nothing about caching/volatility of the quoted price or failure modes beyond a missing posts value.

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 imperative call-to-action is front-loaded in the first sentence and each following sentence adds a distinct fact (no charge, return shape, payment routes). It is dense and slightly long, with the parenthetical OAuth/x402 explanation bordering on verbose, but nothing is filler.

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 no output schema, the description carries the return contract and does so: unit price and total in USD, plus a payment_methods object whose fields it explains. Combined with the annotation-covered safety profile and a fully described 4-parameter schema, an agent has everything needed to call this correctly.

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%, so the schema already documents service_id, service_option_id, quantity, and the posts/per-post multiplication rule, making 3 the baseline. The description adds only the pricing-level note that quantity bounds and rounding are applied here, which is more about behavior than parameter meaning. No extra syntax, defaults, or valid ranges are supplied beyond the schema.

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?

States a specific verb and resource ("Get the exact price that will be charged") and immediately distinguishes itself from the catalog tools by contrasting exact quoted pricing with the per-1000 prices they return. An agent can tell what this does and why it differs from search_catalog/get_service without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when ("Call this before every order") and an explicit when-not ("never total up the per-1000 prices the catalog tools return yourself"), plus the reason (quantity bounds and rounding happen only here). It also routes the agent onward by naming create_paid_order and the REST endpoint for x402 payment and the /mcp endpoint for account-based ordering.

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