core.blue

Prices

pricing

Read-onlyIdempotent

Call this when the person you act for asks what a house costs. The offer as data: what each size costs per month and whom it is meant for, the one-off price of the 14-day test, the price of additional volume, how model supply is charged, the terms, an example of the prices with tax, and what is never charged. 'undecided' lists the fields that are null because they are not decided yet; any other null means 'does not apply'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes	What to keep in mind when quoting from this answer.
`as_of`	Yes	The date this offer was last changed.
`sizes`	Yes	The sizes of a house.
`terms`	Yes	The commercial terms. Null if none are stated.
`manual`	Yes	The version of the manual; cite it in a report.
`source`	Yes	'manual' if this is the offer of the manual, 'operator' if the operator of this server supplied its own.
`stages`	Yes	The stages from first try to a lasting house.
`volume`	Yes	Additional data volume attached to a VM house.
`regions`	Yes	Where the machines stand.
`currency`	Yes	The currency of every amount, as an ISO code. Null if not decided.
`operator`	Yes	Who operates core.blue and sends the invoice.
`undecided`	Yes	The paths of all fields that are null because they are not decided yet. A null field that is not listed here does not apply.
`amounts_are`	Yes	'net' if amounts exclude tax, 'gross' if they include it.
`service_fee`	Yes	The share added to the price of everything bought from a supplier and passed on (volume, tokens): 0.2 means 20 percent.
`model_supply`	Yes	The ways a house can get a language model, and how each is charged.
`gross_example`	Yes	What a customer pays with tax, for one example: whom it is for, the rate, and each size with its prices after tax. An example, not an invoice. Null if the offer gives none.
`never_charged`	Yes	What is never charged for.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description nonetheless adds real interpretive context that no structured field carries: the distinction between 'undecided' nulls and nulls meaning 'does not apply'. It does not discuss caching/freshness of prices, but little else is missing for a static read.

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

Conciseness3/5

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

The trigger is correctly front-loaded, but the single run-on sentence then inventories nearly every field returned, which largely duplicates the output schema. The one genuinely non-obvious sentence (the null semantics) is buried at the end rather than promoted.

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?

With an output schema present, the description need not explain return values, and it covers purpose, trigger, and null interpretation. An agent has enough to call it correctly; only cross-tool routing guidance 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 there is nothing for the description to disambiguate and the schema is trivially complete. Baseline of 4 applies for a parameterless tool.

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 states a specific resource — the pricing/offer data for a house — and enumerates its scope (monthly cost per size, 14-day test one-off, extra volume, model supply charges, terms, tax example, non-charges). It never names or contrasts with siblings such as house_status, about, or recommend, so the agent must infer the boundary itself.

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?

Provides an explicit trigger: 'Call this when the person you act for asks what a house costs.' That is a clear use condition. It stops short of naming when not to use it or which sibling answers adjacent questions (e.g. house_status for availability), so no exclusions are given.

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

All core.blue 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?