AI Admin API MCP Server

ai_admin_query_costs

Read-only

Query normalized cost facts from enabled AI providers. Specify provider-specific options to get cost data for OpenAI and Anthropic.

Instructions

Query normalized cost facts from one or more enabled providers. Pass provider-specific options under provider_options[provider_id].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "ai_admin_query_costs"
  }
}

Input Schema

Name	Required	Description	Default
`end`	Yes
`start`	Yes
`providers`	No
`include_raw`	No
`credential_refs`	No
`provider_options`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Aug 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this as read-only and open-world, so the description's main contribution is noting that it queries 'normalized' cost facts and works with 'enabled' providers. This adds a bit of context but doesn't disclose behaviors like credential requirements, result shape, or rate limits, so it does not go far beyond the annotations.

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

Conciseness5/5

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

Two concise sentences that get straight to the point, front-loading the action and purpose without any filler. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having six parameters, nested objects, and no output schema, the description is minimal and omits important context such as how cost facts are returned, what 'normalized' entails, how multiple providers are specified, and how credentials are handled. This leaves the agent under-informed for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description only references provider_options, one of six parameters. The schema coverage is 0%, but the description does not explain the meaning of start, end, providers, include_raw, or credential_refs, so it fails to compensate for the sparse schema semantics.

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 clearly states a specific action and resource: 'query normalized cost facts' from 'enabled providers.' This distinguishes it from sibling tools that list providers, query usage, or fetch dashboard bundles, making the tool's purpose unambiguous.

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

Usage Guidelines3/5

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

The description implies this tool is for querying cost data and instructs how to pass provider-specific options, but it does not explicitly state when to prefer this over the sibling tools or any exclusions. There is no mention of alternatives or when-not-to-use, so guidance is only implied.

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

Deploy Server