Skip to main content
Glama
pulse-verity

pulse-verity

Get Pulse Verity Account Status

get_account_status
Read-onlyIdempotent

Check your Pulse Verity plan and account-wide monthly usage, including calls used, remaining allowance, reset time, and per-minute/batch limits.

Instructions

Read this developer key's Pulse Verity plan and usage from /api/index/v1/account: plan, used (calls counted this UTC month), limit, remaining, resetAt, perMinute, batchMaxSymbols, capacityAction and upgradeUrl (the plans page). The monthly allowance is account-wide: every key and connected app on the account shares it; perMinute applies to each key. This call does not count toward the allowance. The key itself is never returned. Needs a developer key (PULSE_API_KEY) or the hosted server.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planNoThe plan name customers see, e.g. Developer
usedNoCalls counted this UTC month, account-wide
errorNo
limitNoThe monthly allowance
resetAtNo
successNo
perMinuteNo
remainingNo
requestIdYesIdentifier for this MCP call; not a signed price field.
upgradeUrlNo
capacityActionNo
batchMaxSymbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.3.7
    • removedOutput schema / properties / batchMaxSymbols / $ref
      Removed value: -"#/properties/remaining"
    • addedOutput schema / properties / batchMaxSymbols / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / batchMaxSymbols / minimum
      Added value: +0
    • addedOutput schema / properties / batchMaxSymbols / type
      Added value: +"integer"
    • addedOutput schema / properties / limit / maximum
      Added value: +9007199254740991
    • removedOutput schema / properties / perMinute / $ref
      Removed value: -"#/properties/remaining"
    • addedOutput schema / properties / perMinute / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / perMinute / minimum
      Added value: +0
    • addedOutput schema / properties / perMinute / type
      Added value: +"integer"
    • addedOutput schema / properties / remaining / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / requestId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedOutput schema / properties / used / maximum
      Added value: +9007199254740991
  2. Addedv1.3.6

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: the allowance is account-wide and shared across keys and connected apps while perMinute is per key, this call is free of quota, and the key itself is never returned. That last point is exactly the kind of security behavior structured fields cannot convey.

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?

Front-loaded with verb and resource, then auth and quota semantics. The long comma-separated field list is dense and partially overlaps the output schema, but each item is short and none of the sentences are filler.

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?

For a zero-parameter, explicitly annotated read tool with an output schema, the definition covers the remaining unknowns: auth requirement, quota accounting rules, scope of the allowance, and non-exposure of the key. Nothing an agent needs before calling it 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?

Zero input parameters, so 4 is the baseline. The prose spends its words on the response fields rather than inputs, which is appropriate given there is nothing to parameterize.

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 verb and resource ('Read this developer key's Pulse Verity plan and usage') plus the endpoint path /api/index/v1/account and enumerates exactly what comes back (plan, used, limit, remaining, resetAt, perMinute, batchMaxSymbols, capacityAction, upgradeUrl). An agent can tell immediately this is a read-only account/quota introspection call distinct from the print/index retrieval 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?

Gives concrete context for when this applies: it reads quota state, it does not consume allowance, and it requires a developer key (PULSE_API_KEY) or hosted server. It does not name an alternative tool or an explicit 'do not use for X' exclusion, so a 4 rather than a 5.

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