Skip to main content
Glama

account

Read-onlyIdempotent

The caller's Cubicle account: their tier (free, Cubicle Operators holder, starter-20, pro-50, max premium-99), their plan and until when, and every capability with whether it is open and which tier opens it. Call it before telling a trader what they can or cannot do.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds value beyond that by disclosing the payload shape (tier, plan, expiry, capability matrix), which matters because there is no output schema. It says nothing about authentication failure modes or whether results are cached per session.

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?

Two sentences, front-loaded with the resource and then the action trigger. The parenthetical tier enumeration is dense and includes awkwardly formatted names ('max premium-99'), but it earns its place since no enum exists in the schema to convey valid tier values.

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 no-argument, read-only introspection tool with no output schema, the description is nearly self-sufficient: it states scope, return contents, and the decision it supports. The only gap is absence of any note on behavior when the caller is unauthenticated or has no plan.

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?

With zero parameters there is nothing to disambiguate, and the description correctly frames the result as scoped to 'the caller', implying identity comes from the session rather than arguments. Baseline for a no-parameter tool.

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 the specific resource (the caller's Cubicle account) and enumerates exactly what it returns: tier, plan and its expiry, and per-capability open/closed status with the tier that unlocks each. That is far more than a restatement of the bare name 'account'. It does not, however, differentiate itself from plan- or tier-related siblings such as plans, plan_claim, catalogue, or operator_link.

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?

It gives an explicit trigger condition: call it before telling a trader what they can or cannot do, which anchors the tool to entitlement-gating questions. There is no when-not guidance and no named alternative for adjacent plan/catalogue questions, so it stops short of full routing guidance.

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