Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Workspace usage and entitlements

workspace_usage
Read-onlyIdempotent

The authoritative workspace plan, pricing version, UTC period, included/used/reserved/remaining usage, overages, extra spending limits, site breakdown and maximum normal charges. One shared Research allowance (SEO Research and AI Research); caps authorize additional charges and do not buy credits. Historical financial ownership stays with the originating workspace. Only the workspace Owner can run it.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "workspace_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-redundant behavior: an Owner-only authorization requirement, the clarification that caps authorize additional charges but do not purchase credits, a shared Research allowance across SEO and AI Research, and that historical financial ownership stays with the originating workspace. It stops short of describing response shape or ordering, but the added authorization and billing semantics are substantive.

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?

Four sentences, no filler, and the field inventory is up front where an agent will read it. The opening sentence is a dense 30-word enumeration and phrases like 'maximum normal charges' are opaque without a return schema, but nothing is plainly redundant.

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 by listing the returned data categories, and it supplies the Owner-only prerequisite plus billing semantics. The remaining gaps are modest: no guidance versus sibling usage tools and no detail on the single parameter's expected value.

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?

Schema description coverage is 0% for the single workspaceId parameter, so the description must carry the burden. It repeatedly frames results as workspace-scoped and notes that historical financial ownership stays with the originating workspace, which hints at how workspaceId is interpreted, but it never explains the parameter's format, whether it must be the caller's own workspace, or what happens for a non-owner workspace.

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 enumerates what the tool returns: plan, pricing version, UTC period, included/used/reserved/remaining usage, overages, extra spending limits, site breakdown and maximum normal charges. That makes the resource and scope unambiguous, though no explicit verb is used and nothing distinguishes it from siblings like usage_get or usage_events_by_day.

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 only implied: an agent can infer it should call this to inspect plan entitlements and consumption for a workspace. The description names no alternatives (usage_get, usage_events_by_day, usage_research_log) and states no condition selecting this tool over them, though 'Only the workspace Owner can run it' does give a prerequisite.

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