Skip to main content
Glama

Get account and plan

get_account

Retrieve account plan, credit refresh date, monitor slot usage, available credits, and allowed check frequencies. Use it before creating or changing monitors or to explain a refused create.

Instructions

Who is connected and what their monity.ai plan allows: plan name, credit refresh date, active monitors used and slots left per workspace, check credits left (a check normally costs one), and the check frequencies the plan allows. Use it before creating a monitor or changing a frequency, and to explain a refused create.

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 observedv0.5.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it delivers useful behavioral context: quota semantics ('a check normally costs one'), per-workspace slot consumption, and the plan's frequency limits. It stops short of stating that the call is a side-effect-free read with no credit cost and says nothing about failure behavior.

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?

Two sentences, front-loaded with the identity/plan framing, followed by a single actionable usage clause. The enumerated return fields each earn their place because no output schema exists to document them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no annotations, and no output schema, the description is the only documentation, and it adequately covers both what comes back and why an agent would call it. Nothing essential for correct invocation is missing.

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 zero parameters, so the baseline is 4; the description correctly implies no scoping inputs are needed and all results are scoped to the connected account and its workspaces.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates exactly what the call returns: plan name, credit refresh date, monitor slots used/left per workspace, check credits left, and allowed check frequencies. That is concrete enough for an agent to distinguish this account/plan lookup from the monitor-, check-, and network-oriented siblings.

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 explicit triggering conditions: 'Use it before creating a monitor or changing a frequency, and to explain a refused create.' That covers the main when-to-use cases, but there are no stated exclusions or named alternative tools for edge cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.