GrowVib - Social Media Growth

get_paid_order_status

Read-onlyIdempotent

Track an order placed with create_paid_order: status, start count and remaining quantity, plus a delivery block (the start window the option lists, its bound in minutes, whether delivery has started, and start_overdue when an active order has not started past that bound). Delivery is gradual once it starts and completion time is not estimated, so a falling remains is progress, not a stall. Pass the agent_token that create_paid_order returned (or one from the wallet sign-in at POST /v1/agent/auth/challenge). Read-only and idempotent, so polling it is safe. Statuses: PENDING, SUBMITTED, PROCESSING, COMPLETED, PARTIALLY_COMPLETED, CANCELED, FAILED, PARTIALLY_FAILED, REFUNDED, PARTIALLY_REFUNDED.

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": {
      "order_id": "<order_id>",
      "agent_token": "<agent_token>"
    },
    "name": "get_paid_order_status"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes	The order_id from create_paid_order.
`agent_token`	Yes	The agent_token from create_paid_order's result, or from the wallet sign-in. It proves which wallet is asking; an order that is not this wallet's is reported as not found.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026
RemovedOct 27, 2026

Changed2 schema fields changedSep 13, 2026

changedInput schema / properties / agent_token / description

Previous value: -"The agent_token from place_paid_order's result, or from the wallet sign-in. It proves which wallet is asking; an order that is not this wallet's is reported as not found."New value: +"The agent_token from create_paid_order's result, or from the wallet sign-in. It proves which wallet is asking; an order that is not this wallet's is reported as not found."

changedInput schema / properties / order_id / description

Previous value: -"The order_id from place_paid_order."New value: +"The order_id from create_paid_order."

AddedSep 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, and non-destructive, but the description adds genuinely new behavioral context: delivery is gradual, completion time is not estimated, a falling remaining quantity is progress rather than a stall, and an order belonging to another wallet is reported as not found. The full status enumeration also prepares the agent for every response state.

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?

Content is front-loaded with the return shape, then caveats, then auth, then statuses, and nearly every sentence carries information. The deeply nested parenthetical describing the delivery block is dense and slightly harder to parse than necessary, 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?

There is no output schema, so the description must carry the return shape, and it does — naming each returned field and explaining how to interpret the delivery block and remaining quantity. Auth requirements, safety profile, and status vocabulary are all present, so nothing an agent needs to call and interpret this tool is missing.

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% and both parameters are already documented with their origins. The description adds provenance detail (the auth challenge endpoint) and reinforces the wallet-scoping consequence, but it mostly restates what the schema already conveys. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description opens with a specific verb and resource ('Track an order placed with create_paid_order') and enumerates exactly what is returned: status, start count, remaining quantity, and the delivery block fields. It also names the sibling that creates the order, so an agent can distinguish it from checkout-oriented siblings like get_checkout_status.

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 states the operational context clearly — poll this to follow an order, and polling is safe because the call is read-only and idempotent — plus where to get the agent_token. It does not explicitly contrast with list_paid_orders or get_checkout_status, so the when-not guidance is implied rather than stated.

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?