Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Billing for one site

billing_site
Read-onlyIdempotent

The site's plan, who pays for it (youPay), the billing profile and card when you pay, its spend caps, and this month's usage. sites.ceilings.set changes the site's limits. People change plans and payment in the app.

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": {
      "siteId": "<siteId>"
    },
    "name": "billing_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's main burden is to add operational context. It does so by naming the returned billing areas, noting that card/profile appear 'when you pay', and clarifying that limits, plans, and payment changes happen outside this tool. It does not discuss permissions, freshness, or formatting details, but adds useful boundaries 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.

Conciseness4/5

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

The description is short and front-loaded, beginning with the core billing data available for a site. It uses compact noun-phrase lists and then adds two useful boundary statements. There is little wasted wording, though the first sentence is slightly dense.

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 single-parameter read tool, the description adequately enumerates the kinds of returned information even without an output schema. Annotations cover the safety profile. However, the missing explanation of 'siteId' and lack of explicit usage guidance leave some gaps for an agent selecting and invoking it.

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?

There is one required parameter, 'siteId', and schema description coverage is 0%, so the description needs to explain what the parameter means or where to obtain it. The description refers to 'the site' but never explicitly defines 'siteId', its expected format, or any lookup source. This leaves the only input under-documented.

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 identifies the resource and returned information: plan, payer, billing profile/card, spend caps, and current-month usage for one site. It also distinguishes this read operation from the mutating 'sites.ceilings.set' tool. The main gap is that it does not explicitly differentiate itself from similarly named account-level billing reads such as 'account_get'.

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?

Usage is implied: use this to inspect one site's billing data. The description helpfully says that limits are changed by 'sites.ceilings.set' and that people change plans/payment in the app, which implicitly routes mutation use cases elsewhere. However, it does not give explicit when-to-use or when-not-to-use guidance versus other read tools.

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.

Resources