model_detailGet capabilities, context/output limits, and current sourced provider offers by model_slug from catalog_search. Prices are base-context rates; long-context tiers, cache writes, batch discounts, and free-tier quotas can change actual cost.
| Name | Required | Description | Default |
|---|---|---|---|
| model_slug | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| meta | Yes |
Changes observed during successful MCP inspections.
Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / model_slug / patternAdded value: +"^[a-zA-Z0-9._:-]+$"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "properties": {
+ "model": {
+ "properties": {
+ "author": {
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "name"
+ ],
+ "type": "object"
+ },
+ "capabilities": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "categories": {
+ "items": {
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "name"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "contextTokens": {
+ "anyOf": [
+ {
+ "minimum": 1,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "description": {
+ "type": "string"
+ },
+ "family": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "type": "string"
+ },
+ "knowledgeCutoffAt": {
+ "anyOf": [
+ {
+ "format": "date",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "maxOutputTokens": {
+ "anyOf": [
+ {
+ "minimum": 1,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "offers": {
+ "items": {
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "limits": {
+ "properties": {
+ "contextTokens": {
+ "anyOf": [
+ {
+ "minimum": 1,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "maxOutputTokens": {
+ "anyOf": [
+ {
+ "minimum": 1,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "contextTokens",
+ "maxOutputTokens"
+ ],
+ "type": "object"
+ },
+ "model": {
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "name"
+ ],
+ "type": "object"
+ },
+ "prices": {
+ "properties": {
+ "cachedInputPerMillionTokens": {
+ "anyOf": [
+ {
+ "minimum": 0,
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "inputPerMillionTokens": {
+ "minimum": 0,
+ "type": "number"
+ },
+ "outputPerMillionTokens": {
+ "minimum": 0,
+ "type": "number"
+ }
+ },
+ "required": [
+ "inputPerMillionTokens",
+ "outputPerMillionTokens",
+ "cachedInputPerMillionTokens"
+ ],
+ "type": "object"
+ },
+ "provenance": {
+ "properties": {
+ "checkedAt": {
+ "format": "date",
+ "type": "string"
+ },
+ "sourceUrl": {
+ "format": "uri",
+ "type": "string"
+ }
+ },
+ "required": [
+ "sourceUrl",
+ "checkedAt"
+ ],
+ "type": "object"
+ },
+ "provider": {
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "name"
+ ],
+ "type": "object"
+ },
+ "routeType": {
+ "enum": [
+ "official",
+ "cloud",
+ "gateway",
+ "unverified"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "model",
+ "provider",
+ "routeType",
+ "prices",
+ "limits",
+ "provenance"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "releaseChannel": {
+ "type": "string"
+ },
+ "releasedAt": {
+ "anyOf": [
+ {
+ "format": "date",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "slug": {
+ "type": "string"
+ },
+ "status": {
+ "type": "string"
+ },
+ "weightAvailability": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "slug",
+ "name",
+ "description",
+ "author",
+ "family",
+ "status",
+ "releaseChannel",
+ "releasedAt",
+ "knowledgeCutoffAt",
+ "contextTokens",
+ "maxOutputTokens",
+ "weightAvailability",
+ "capabilities",
+ "categories",
+ "offers"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "model"
+ ],
+ "type": "object"
+ },
+ "meta": {
+ "properties": {
+ "apiVersion": {
+ "const": "v1"
+ },
+ "currency": {
+ "const": "USD"
+ },
+ "tokenPriceUnit": {
+ "const": "per_million_tokens"
+ }
+ },
+ "required": [
+ "apiVersion",
+ "currency",
+ "tokenPriceUnit"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "meta",
+ "data"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds non-obvious context the annotations cannot: that prices are base-context rates and that long-context tiers, cache writes, batch discounts, and free-tier quotas can change real cost — an important caveat for interpreting results.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the capability statement and followed by the pricing caveat. No filler, and both sentences carry distinct information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-shape explanation is unnecessary, and rich annotations cover the safety profile. Given a single required parameter, the description supplies purpose, input provenance, and a cost-interpretation caveat — everything needed to call and read the result correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With one parameter and 0% schema description coverage, the schema supplies only a pattern and length bound. The description compensates by disclosing provenance ('by model_slug from catalog_search'), which is the meaning an agent most needs beyond the raw format constraints, though it adds no further syntax detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb (Get) and enumerates exactly what the resource returns: capabilities, context/output limits, and current sourced provider offers. It also ties the lookup key back to catalog_search, which separates it from that sibling and from offer_compare, 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives a clear prerequisite — model_slug comes from catalog_search — which tells the agent when this tool is callable. It does not state explicit exclusions or contrast with siblings like offer_compare/provider_list, so it falls short of a full when/when-not statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.