Skip to main content
Glama

Account Status

account-status
Read-onlyIdempotent

Return the connected account's plan, quota availability, enabled features, limits and usage counts.

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-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoWhy you are calling this tool, in a few words. No names or emails.
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
planNo
usageNo
limitsNo
featuresNo
has_quotaNo
quota_statusNo
cycle_ends_atNo
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "cycle_ends_at": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "features": {
      +    "additionalProperties": {
      +      "type": "boolean"
      +    },
      +    "required": [],
      +    "type": "object"
      +  },
      +  "has_quota": {
      +    "type": "boolean"
      +  },
      +  "limits": {
      +    "properties": {
      +      "company_exclusion_list_size": {
      +        "type": "integer"
      +      },
      +      "contact_exclusion_list_size": {
      +        "type": "integer"
      +      }
      +    },
      +    "required": [],
      +    "type": "object"
      +  },
      +  "plan": {
      +    "type": "string"
      +  },
      +  "quota_status": {
      +    "type": "string"
      +  },
      +  "usage": {
      +    "properties": {
      +      "account_status": {
      +        "type": "string"
      +      },
      +      "month_to_date_records": {
      +        "type": "integer"
      +      },
      +      "month_to_date_requests": {
      +        "type": "integer"
      +      },
      +      "recent_companies_billed": {
      +        "type": "integer"
      +      },
      +      "recent_contacts_billed": {
      +        "type": "integer"
      +      },
      +      "recent_emails_billed": {
      +        "type": "integer"
      +      },
      +      "recent_records_billed": {
      +        "type": "integer"
      +      },
      +      "usage_summary": {
      +        "additionalProperties": {
      +          "items": {
      +            "properties": {
      +              "access_id": {
      +                "type": "string"
      +              },
      +              "description": {
      +                "type": "string"
      +              },
      +              "requests": {
      +                "type": "integer"
      +              },
      +              "total_records": {
      +                "type": "integer"
      +              }
      +            },
      +            "required": [],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "required": [],
      +        "type": "object"
      +      }
      +    },
      +    "required": [],
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds only the enumeration of returned data, which largely duplicates the output schema, and says nothing about freshness, caching, or what happens on an expired/unauthenticated account.

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?

A single front-loaded sentence with no filler, and the highest-value information (what data comes back) is stated first. It is efficient, though it packs a bare list with no structuring for the more important fields.

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

Completeness3/5

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

With an output schema present, the return values need no further explanation and annotations cover the safety profile. However, for a status tool that agents typically call to gate other operations, the definition omits when to use it and whether it is cheap or rate-limited, leaving a meaningful gap.

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 100% and all three parameters (context, llm_model, conversation_id) are documented in the schema as telemetry-style fields. The description adds no meaning about these parameters, but with full schema coverage the baseline of 3 applies.

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 uses a specific verb ('Return') and names the exact resource and field set (plan, quota availability, enabled features, limits, usage counts). An agent can tell this is a read-only account introspection tool without opening the schema, though it does not explicitly distinguish itself from the sibling 'usage-statistics'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus alternatives such as 'usage-statistics' or 'growth-metrics', no prerequisites, and no statement about whether calling it consumes quota or requires authentication state. The intended use (checking plan/quota before a bulk operation) must be inferred.

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