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": {
      "service_id": "<service_id>",
      "quantity": "<quantity>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description
`posts`	No	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.
`quantity`	Yes	Quantity to order (e.g. number of members or views).
`service_id`	Yes	The service id from search_catalog.
`service_option_id`	No	Optional specific service option id; defaults to the service's primary option.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

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

First observedSep 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already declare readOnly/idempotent/non-destructive, and the description adds real context: no order is placed, nothing is charged, and pricing runs through the same server-side path a real order uses. It also explains the payment_methods branches (OAuth account vs. x402 on Base/Solana) that an agent must interpret since there is no output schema. Minor deduction because it does not discuss rate limits or quote validity/expiry.

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 critical instruction (call before ordering, don't self-compute) is front-loaded in the first two sentences. The trailing payment_methods sentence is dense and long but earns its place as the only documentation of the return shape.

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-value burden and does so: unit price, total in USD, and the nested payment_methods/x402 structure are explained. Nothing an agent needs to call it correctly or interpret the response is missing.

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 baseline is 3; the description still adds meaning by saying quantity bounds and rounding are applied here and nowhere else, which explains why local arithmetic is invalid. The posts parameter is well covered by the schema itself, so the description adds little there.

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 — compute the exact price that will be charged — and immediately scopes it against siblings: it is not the catalog's per-1000 math and it places no order. An agent can distinguish it from search_catalog, create_checkout, and create_paid_order without opening any 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?

"Call this before every order" gives an explicit trigger, and "never total up the per-1000 prices the catalog tools return yourself" explicitly forbids the wrong alternative. It also routes onward, naming create_paid_order and the REST endpoint for the x402 case, so the use/do-not-use boundary is fully specified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GrowVib - Social Media Growth tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?