Velarion Company Intelligence

List the product catalog

list_skus

Read-onlyIdempotent

List the Velarion product catalog.

Returns every report this token can order with place_order under sellable, with full detail (name, price, currency, delivery type, latency, caveats). Reports on sale but not orderable over MCP are under buy_on_web, each with the buy_url a human buys it at. Set include_non_sellable=true to also return products that are not currently on sale, each tagged with its status, so the full range is visible. A product with no settled price is returned with its status rather than a billable number.

Input Schema

Name	Required	Description	Default
`agent_token`	No	Optional Velarion agent token; falls back to the X-Velarion-Agent-Token header.
`include_non_sellable`	No	Also return products that are not currently on sale.

Output Schema

Name	Required	Description
`error`	No
`counts`	No
`sellable`	No	Products this token can order with place_order.
`buy_on_web`	No	Products on sale but not orderable over MCP, each with the buy_url a human buys it at.
`attribution`	No	Source citation, dataset DOI, and a ready-made cite_as string.
`non_sellable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / buy_on_web

Added value: +{
+  "description": "Products on sale but not orderable over MCP, each with the buy_url a human buys it at.",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / sellable / description

Previous value: -"Products currently on sale."New value: +"Products this token can order with place_order."

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. Beyond that, the description adds useful behavioral context: reports are grouped into `sellable` versus `buy_on_web`, non-sellable items are tagged with status, and products without settled prices are returned as status rather than billable amounts.

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 description is front-loaded with the core action and then expands into catalog behavior. It is somewhat long but every major sentence contributes useful information about grouping, conditional inclusion, and edge-case pricing.

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?

Given the presence of an output schema, the description does not need to document every return field. It still covers the major output categories, the conditional parameter, and the no-settled-price edge case, making the tool's behavior complete enough for correct invocation.

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 the parameters are already documented. The description still adds meaning to `include_non_sellable` by explaining that it exposes the full catalog range and that non-sale products carry status tags; `agent_token` is only weakly elaborated 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?

The description gives a specific verb and resource: listing the Velarion product catalog. It immediately distinguishes the object being returned and explains the key catalog groupings (`sellable`, `buy_on_web`), so an agent can tell what this tool does without opening the schema.

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?

The description clearly states when to set `include_non_sellable=true`, namely to include products not currently on sale and see the full range. It does not name an alternative tool, but the sibling tools are unrelated governance/compensation tools, so there is no meaningful sibling choice to route between.

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

All Velarion Company Intelligence 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?