Skip to main content
Glama

NS Pros MCP Gateway

golfcore__api_budget

Starter and Pro have no monthly cap by default: requests past the included amount are billed at the plan's overage rate without limit. This tool sets an optional cap, after which requests are refused until the month resets, or removes it when units is null. A cap starts at the plan's included requests (read them from api_account). Confirm the number and what it could cost with the person first.

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": {
      "account_id": "<account_id>",
      "units": "<units>"
    },
    "name": "golfcore__api_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYesMonthly request cap, or null for no cap.
account_idYesFrom api_account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the consequence of setting a cap (requests refused until the month resets), how to undo it (units null), and the default billing behavior that motivates the tool. It does not cover auth/permission requirements or what the tool returns, which is a gap for a mutation tool.

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?

Three short sentences plus a caution, front-loaded with the billing context that justifies the tool, then the action, then the safety instruction. The opening sentence is background rather than action, but it earns its place by explaining why the cap exists.

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

Completeness4/5

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

For a two-parameter mutation tool with no annotations or output schema, the description covers consequences, reversal, prerequisites, and human confirmation. The remaining gap is the immediate effect on the current billing period and the response shape, neither of which is disclosed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: units null means remove the cap, and a cap should start at the plan's included requests read from api_account. That links the parameter value to a concrete source rather than leaving the agent to guess an arbitrary number.

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 and resource: it sets or removes an optional monthly request cap on an account. It also separates the read path from the write path by pointing to api_account for the included amount, so an agent can distinguish intent without opening another schema.

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

Usage Guidelines4/5

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

Gives clear when-to-use context (optional cost-control cap on Starter/Pro, which otherwise have unlimited overage billing) and when-to-remove (passing units as null). It also tells the agent to source the starting number from api_account and to confirm cost impact with the person first. It stops short of naming sibling alternatives for account changes, but the guidance is unusually complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.