Skip to main content
Glama
Sign In
GPT-5 MCP Server

GPT-5 MCP Server

by andreahaku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_cost_report

Receive a cost and usage report for the current task, day, week, or month. Use it to monitor spending and track resource consumption.

Instructions

Get a report of current costs and usage

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": {
      "period": "<period>"
    },
    "name": "get_cost_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYesThe period to report on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only states 'Get a report' without detailing return format, how 'current' is interpreted relative to the period parameter, or any other behavioral traits such as read-only nature or potential side effects.

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?

The description is a single concise sentence, front-loaded with the action and resource. Every word earns its place, and there is no redundancy.

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

Completeness3/5

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

For a simple read-only tool with one parameter and no output schema, the description is minimally viable. However, it leaves gaps: it does not explain what 'costs and usage' includes, whether the report is aggregate or detailed, or how the period parameter affects the output. This is adequate but not complete.

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?

The schema has 100% coverage for the single parameter 'period' with a clear description and enum. The tool description itself adds no parameter information, so it meets the baseline of 3 without enhancing semantic understanding.

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 clearly states the tool's function with a specific verb ('Get') and resource ('report of current costs and usage'). It is distinct from sibling tools like set_cost_limits and get_conversation_metadata, though it could more explicitly delineate its scope compared to those.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. Sibling tools exist (e.g., set_cost_limits), but the description does not mention exclusions or direct users to alternative tools for other use cases.

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

Deploy Server

Other Tools