Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Usage and limits

usage_get
Read-onlyIdempotent

This site’s events, recordings and Research (SEO Research and AI Research) usage in the current billing period, its optional limits, and explicitly shared workspace capacity. Null limits mean no local ceiling; zero pauses that category. Workspace financial details remain Owner-only. Legacy sites retain separate monthly allowances. Editor or higher.

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": "usage_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower. The description adds genuinely useful semantics beyond them: what null and zero mean for limits, that financial details are Owner-only, and that legacy sites keep separate monthly allowances. It does not describe the response shape or granularity of aggregation, but that is a minor gap for a read-only 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?

The scope statement is front-loaded in the first sentence and the remaining clauses each carry distinct meaning (limit semantics, permissions, legacy behavior). Semicolon-dense phrasing makes it slightly harder to scan, but there is no filler.

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 read-only, single-parameter tool with no output schema, the description covers what data categories come back, how limits should be read, and who may access what. The remaining gap is the siteId contract, which the description leaves entirely to the bare schema.

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 single siteId parameter has 0% schema description coverage, so the description must carry the burden. 'This site's' establishes that the tool is scoped to one site, which is minimal but correct compensation. It gives no format, source, or validity guidance for siteId itself.

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 names a specific resource and scope: events, recordings, SEO/AI Research usage for the current billing period, plus optional limits and shared workspace capacity. It reads clearly as a per-site usage/limits summary. It stops short of explicitly distinguishing itself from siblings such as usage_events_by_day, usage_research_log or workspace_usage, leaving that differentiation implicit.

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 rather than stated: an agent can infer this is the place to get an aggregate usage/limits snapshot for one site. The access prerequisite 'Editor or higher' and the note that financial details stay Owner-only add practical context. There is no explicit when-to-use versus the granular usage_* siblings.

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