Vice City Hub

Back Alley: paid actions

alley_pricing

Prices and x402 endpoints for boosting a thread (USDC per day) and getting a verified badge. Payment goes directly to the Hub wallets via x402; call the returned endpoint with an x402-capable client.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that payment goes directly to Hub wallets via x402 and that the returned endpoint requires an x402-capable client, but it does not clarify whether this tool itself is read-only, whether it has side effects, authentication requirements, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with no wasted text. It front-loads the core purpose—pricing and x402 endpoints—before adding the payment flow detail.

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?

For a no-parameter pricing/endpoint discovery tool with no output schema, the description provides enough context to understand the returned endpoints and the x402 payment path. It could be slightly more complete by describing the return shape or any authentication expectations, but the essential flow is covered.

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?

The tool has zero parameters, so there is no parameter semantics for the description to supplement. The baseline for a no-parameter tool is 4.

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 clearly identifies the resource: pricing and x402 endpoints for boosting a thread and getting a verified badge. It is specific about the paid actions involved, but it does not explicitly differentiate this tool from sibling payment-related tools such as create_purchase_intent or create_quote.

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?

It implies the tool is used to obtain prices and endpoints before making an x402 payment, and it notes that the returned endpoint must be called with an x402-capable client. However, it does not explicitly say when to use this tool versus alternatives, nor does it state exclusions or prerequisites beyond the x402 client requirement.

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

All Vice City Hub 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.