BlockVectra Docs

Get Plans and Pricing

get_pricing

Read-only

Live prices and plan limits from GET /v1/plans. Use before estimating cost or when asked about free credits, rate limits or per-method prices. Units: 1 billing unit = pricing.cu_per_unit CU; 1 USD buys pricing.units_per_usd units. method_weights is CU per call; resolve a method by exact match, then the longest prefix rule ending in *, then the * row (JSON-RPC only; Data API operations have no default). free.* values are in billing units; key_defaults are per-key CU/s and burst CU. promo.ends_at is a sign-up coverage cutoff, not the end of the offer.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`free`	No
`pricing`	Yes
`key_defaults`	No
`method_weights`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties
```
Removed value: -{}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "free": {
+      "type": "object"
+    },
+    "key_defaults": {
+      "type": "object"
+    },
+    "method_weights": {
+      "type": "array"
+    },
+    "pricing": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "pricing",
+    "method_weights"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes well beyond them by disclosing billing-unit semantics, method_weights resolution order, free.* units, key_defaults burst semantics, and the promo.ends_at caveat — real interpretation context not present in structured fields.

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?

Purpose and usage lead, with unit/return semantics following, so it is well front-loaded. It is dense with semicolon-chained clauses and spends several sentences on return-value interpretation that a present output schema may already carry, so it is slightly heavier than strictly necessary for a no-argument tool.

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?

For a zero-parameter read tool with annotations and an output schema, the description supplies exactly the missing layer — when to invoke it and how to read the units and lookup rules. Nothing needed to call or interpret it correctly is absent.

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 takes zero parameters, so the baseline is 4 per the rubric. The description adds no parameter meaning because there are none to add, and the empty schema is self-explanatory.

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 resource and source endpoint ('Live prices and plan limits from GET /v1/plans'), and its scope is clearly distinguishable from siblings like estimate_usage, which it explicitly routes against by naming the cost-estimation context.

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?

Gives explicit trigger conditions: 'Use before estimating cost or when asked about free credits, rate limits or per-method prices.' It does not name the sibling tool (estimate_usage) as an alternative or state when not to use it, so it stops short of a full 5.

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

All BlockVectra Docs 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?