Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

This site’s usage limits

sites_ceilings_get
Read-onlyIdempotent

Read this site’s event, recording and Research limits, own usage and remaining shared workspace capacity. Null means no site limit; zero pauses that category. Site Admin or Owner. Does not expose unrelated sites or the workspace bill.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, and the description goes beyond them by explaining sentinel semantics ('Null means no site limit; zero pauses that category') and the required role (Site Admin or Owner). The scope disclaimer about not exposing unrelated sites or the bill further clarifies what an agent will and won't see.

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?

Three compact sentences with the primary payload front-loaded, followed by interpretation rules and scope/permission constraints. No filler or repetition of the title, and every clause carries distinct information.

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?

With no output schema, the description does the necessary work of naming the returned categories and explaining null/zero sentinel values, plus access requirements — enough for correct invocation. It stops short of describing response shape or ordering, but nothing critical for calling the tool is missing.

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?

Only one parameter (siteId) exists and the schema carries zero description coverage, so the description must compensate; it only implies scope via 'this site's' without stating that siteId selects the target site or what form the identifier takes. The role note indirectly hints at permission requirements on the identifier, but format and expected value are left unstated.

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 gives a specific verb ('Read') and enumerates the exact resources returned: event, recording and Research limits, own usage, and remaining shared workspace capacity. The closing sentence excludes workspace-level content ('Does not expose unrelated sites or the workspace bill'), which helps separate it from billing/workspace tools, though no sibling is named directly.

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 by the phrasing 'this site's ... limits' and the Site Admin/Owner prerequisite gives useful access context. However, it never says when to pick this over nearby tools such as usage_get, workspace_usage, or billing_site, and offers no explicit exclusions beyond the bill.

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