Skip to main content
Glama

Callboard account

get_account
Read-onlyIdempotent

The signed-in promoter's plan and how many briefs they can run: the free briefs a new account starts with, the plan's allowance this period, and any briefs bought in a pack. When none are left, message says how to get more. Call this before run_brief when you don't know the remaining allowance.

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

Output Schema

NameRequiredDescriptionDefault
planYes
teamNo
emailNo
quotaNo
messageNoSet when the account has no briefs left to run: how to get more
is_adminNo
mcp_enabledNo
access_levelYes
purchased_briefsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / $defs / Quota / properties / scope / description
      Previous value: -"'user' for Scout, 'team' for Buyer/Company"New value: +"'user' for free accounts and Scout, 'team' for Buyer/Company"
    • addedOutput schema / properties / mcp_enabled / default
      Added value: +true
    • changedOutput schema / properties / message / description
      Previous value: -"Set when the plan does not include Claude access"New value: +"Set when the account has no briefs left to run: how to get more"
    • changedOutput schema / required
      Previous value: -[
      -  "plan",
      -  "access_level",
      -  "mcp_enabled"
      -]New value: +[
      +  "plan",
      +  "access_level"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / $defs / PurchasedBriefs
      Added value: +{
      +  "properties": {
      +    "expires_at": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "The whole purchased balance expires at this time (12 months after the last purchase)",
      +      "title": "Expires At"
      +    },
      +    "remaining": {
      +      "description": "Briefs bought in packs that can still be used. Spent only after the plan's allowance runs out.",
      +      "title": "Remaining",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "remaining"
      +  ],
      +  "title": "PurchasedBriefs",
      +  "type": "object"
      +}
    • addedOutput schema / properties / purchased_briefs
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/PurchasedBriefs"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered. The description adds genuine context beyond that: it reveals the response decomposes into three allowance buckets and that an exhausted account returns an upgrade/how-to-get-more message, which shapes how an agent should react to the result.

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 what is returned and closing with the actionable usage rule. The colon-separated list of allowance sources is efficient, though slightly dense for a reader skimming for the trigger condition.

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?

An output schema exists, yet the description still summarizes the meaningful return shape (three allowance categories plus an exhaustion message) and pairs it with the decision rule for calling. For a zero-parameter, read-only tool this leaves nothing an agent needs unresolved.

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 there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies no arguments are needed by framing the call as 'call this before run_brief' with no inputs specified.

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?

States a specific resource (the signed-in promoter's plan) and enumerates exactly what it returns: free briefs, plan allowance for the period, and purchased packs. That inventory of fields distinguishes it cleanly from siblings like get_brief or list_briefs, which return content rather than entitlement state.

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?

Explicitly directs the agent to call it before run_brief when the remaining allowance is unknown, which is a concrete trigger tied to a named sibling. It stops short of stating the inverse case (skip it when allowance is already known) or what to do when the count is exhausted beyond noting a message exists.

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