Hubris

This connector has been deprecated

This connector is a duplicate. Use Hubris instead — same endpoint (https://api.hubris.pw/mcp), but with ownership verified, OAuth, all five tools inspected and a quality score.

Get model pricing

models_get_pricing

Read-onlyIdempotent

The full price of one model in rubles — the authoritative answer to "what does this cost".

Prefer this over the pricing embedded in models_list and models_search whenever the model is not billed per token. Those two return "0.00" token rates for such models; only this tool returns perUnit, where the real price per image, per second or per thousand characters lives.

For speech models it also lists the voices speech_create accepts (supportedVoices), for video models the durations, resolutions and aspect ratios video_create accepts (video).

Errors with InvalidParams if the model id is unknown or the model is no longer active.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`modelId`	Yes	Exact model id from the catalogue, vendor included, e.g. "openai/gpt-6-astra".

Output Schema

TableJSON Schema

Name	Required	Description
`unit`	Yes	Billing unit. "token" — priced per token, the two Rub fields below are meaningful. "unit" — priced per image, per minute, per character and so on; token fields are "0.00" and the real price is in models_get_pricing → perUnit. "unknown" — no pricing on record.
`video`	No	Video models only: the values video_create accepts for this model.
`isFree`	Yes	True only for genuinely free models. Do not infer this from a zero price: models billed per image or per minute also report "0.00" token rates.
`perUnit`	No	Present only for models not billed per token. This is where their real price lives.
`currency`	Yes	All prices are in rubles.
`inputPer1MRub`	Yes	Price of 1M input tokens in rubles, decimal string, e.g. "182.40". "0.00" when unit is not "token".
`outputPer1MRub`	Yes	Price of 1M output tokens in rubles, decimal string. "0.00" when unit is not "token".
`supportedVoices`	No	Speech models only: voice names to pass as `voice` to speech_create. Absent when the model has no list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedOutput schema / properties / supportedVoices

Added value: +{
+  "description": "Speech models only: voice names to pass as `voice` to speech_create. Absent when the model has no list.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / video

Added value: +{
+  "additionalProperties": false,
+  "description": "Video models only: the values video_create accepts for this model.",
+  "properties": {
+    "aspectRatios": {
+      "description": "Allowed `aspect_ratio` values, e.g. \"16:9\". Empty when not selectable.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "durations": {
+      "description": "Allowed `duration` values in seconds. Empty when the model does not take this parameter.",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "generateAudio": {
+      "description": "Whether `generate_audio` is available on this model.",
+      "type": "boolean"
+    },
+    "resolutions": {
+      "description": "Allowed `resolution` values, e.g. \"720p\". Empty when not selectable.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "seed": {
+      "description": "Whether `seed` is available on this model.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "durations",
+    "resolutions",
+    "aspectRatios",
+    "generateAudio",
+    "seed"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / modelId / description

Added value: +"Exact model id from the catalogue, vendor included, e.g. \"openai/gpt-6-astra\"."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "currency": {
+      "const": "RUB",
+      "description": "All prices are in rubles.",
+      "type": "string"
+    },
+    "inputPer1MRub": {
+      "description": "Price of 1M input tokens in rubles, decimal string, e.g. \"182.40\". \"0.00\" when unit is not \"token\".",
+      "type": "string"
+    },
+    "isFree": {
+      "description": "True only for genuinely free models. Do not infer this from a zero price: models billed per image or per minute also report \"0.00\" token rates.",
+      "type": "boolean"
+    },
+    "outputPer1MRub": {
+      "description": "Price of 1M output tokens in rubles, decimal string. \"0.00\" when unit is not \"token\".",
+      "type": "string"
+    },
+    "perUnit": {
+      "description": "Present only for models not billed per token. This is where their real price lives.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "priceRub": {
+            "description": "Price of one unit in rubles, decimal string.",
+            "type": "string"
+          },
+          "sku": {
+            "description": "What exactly is billed, e.g. \"image\", \"video\", \"speech\".",
+            "type": "string"
+          },
+          "unit": {
+            "description": "Unit of billing, e.g. \"image\", \"second\", \"1k characters\".",
+            "type": "string"
+          }
+        },
+        "required": [
+          "sku",
+          "unit",
+          "priceRub"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unit": {
+      "description": "Billing unit. \"token\" — priced per token, the two Rub fields below are meaningful. \"unit\" — priced per image, per minute, per character and so on; token fields are \"0.00\" and the real price is in models_get_pricing → perUnit. \"unknown\" — no pricing on record.",
+      "enum": [
+        "token",
+        "unit",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "unit",
+    "inputPer1MRub",
+    "outputPer1MRub",
+    "isFree",
+    "currency"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral content beyond them: the error contract (InvalidParams for unknown or inactive models) and the fact that this tool uniquely returns `perUnit`, `supportedVoices`, and `video`.

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?

Front-loaded with the core answer and then the routing rule, with no filler sentences. The opening phrase about being the 'authoritative answer to what does this cost' is slightly rhetorical but still does work toward intent.

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?

An output schema exists, so return values need not be enumerated, yet the description usefully flags where the meaningful fields live. Error behavior is stated, and the cross-tool relationships (speech_create, video_create) are made explicit. Nothing needed to call it correctly 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 description coverage is 100% and the single `modelId` parameter is already documented as an exact catalogue id with a vendor prefix. The description adds no format, casing, or fallback guidance beyond what the schema states, so the baseline 3 applies.

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 verb ('Get') and resource ('model pricing') and pins the scope: the full price of one model in rubles. It explicitly distinguishes itself from sibling pricing paths (models_list, models_search), so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit preference rule: use this over models_list/models_search whenever the model is not billed per token, with the concrete symptom ('0.00' token rates) that indicates the wrong tool. It also names the downstream consumers (speech_create, video_create) whose accepted inputs are surfaced here.

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

All Hubris 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.