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

GPT-5 MCP Server

by andreahaku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_cost_limits

Set per-task and daily spending limits in USD to manage GPT-5 usage costs and avoid budget overruns.

Instructions

Configure spending limits for GPT-5 usage

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_cost_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_limitNoPer-task spending limit in USD
daily_limitNoDaily spending limit in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies mutation via 'Configure' but does not state whether this overwrites existing limits, requires specific permissions, or has any side effects. It also does not describe the response or error behavior.

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 that front-loads the action and resource. There is no filler, redundancy, or unnecessary detail. It is appropriately sized for the tool's simplicity.

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?

The tool is simple with only two optional parameters and no output schema, so the description is close to adequate. However, it lacks usage guidelines and behavioral transparency, making it minimally viable but not fully complete for confident invocation in all scenarios.

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 already provides 100% coverage with clear descriptions for both parameters (task_limit and daily_limit in USD). The description adds only the context that these are for GPT-5 usage, which is minimal additional meaning beyond the schema.

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 uses a specific verb 'Configure' with resource 'spending limits for GPT-5 usage', clearly distinguishing it from sibling tools like get_cost_report (which reports costs) and set_conversation_options (which sets conversation options). The scope is unambiguous.

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. It does not mention exclusions, prerequisites, or relationships to siblings like get_cost_report for viewing limits or set_conversation_options for other settings. The usage context is entirely implied.

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