Skip to main content
Glama

Get account and plan

get_account
Read-only

Returns the WebDesk account name, the person's role, the current plan, its limits, how many sites are used, and the plans page link.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by enumerating the six fields in the response, which matters because there is no output schema. It stops short of disclosing auth requirements, error behavior for unauthenticated callers, or whether site counts are account-wide or user-scoped.

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?

One sentence that front-loads the resource and then lists the payload contents in a compact, scannable enumeration. Every clause corresponds to a distinct returned field, so nothing is padding.

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 zero-argument read tool with no output schema and full annotation coverage, describing the returned fields is essentially the complete job. Minor omission: it does not clarify scoping (account-wide vs. per-person) or what an agent should expect if the account has no plan or the caller lacks access.

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?

The tool takes no parameters, so per the baseline rule this scores 4. The description correctly adds no parameter discussion, keeping focus on the returned content.

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?

Uses a specific verb ("Returns") on a specific resource (the WebDesk account) and enumerates exactly what is returned: account name, role, plan, limits, site usage, and plans page link. This clearly separates it from resource-specific siblings like get_site or get_lead, though it never names those siblings explicitly.

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 this is the tool for account- and plan-level information, but the description gives no explicit when-to-use statement, no exclusions, and no alternatives (e.g., use get_site for per-site data). For a zero-parameter read tool the intent is fairly self-evident, so this is a moderate gap rather than a serious one.

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