Skip to main content
Glama

BetterPost

by ai.betterpost

Get usage

betterpost_get_usage
Read-only

Your credit balance, freeze state, and recent spend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
frozenYes
creditBalanceYes
recentSpendUsdYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • removedInput schema / properties / token
      Removed value: -{
-  "description": "Your saved BetterPost token from a prior call (demo `bp_demo_…` or paid `bp_live_…`). Reuse the same token on every call and across conversations; omit only on the very first call to be issued a free demo token. Paid users may instead pass the key in the server URL (?key=…) or an Authorization: Bearer header.",
-  "type": "string"
-}
    • removedOutput schema / properties / _note
      Removed value: -{
-  "description": "One-time note — e.g. a freshly issued demo token to save to durable memory and reuse.",
-  "type": "string"
-}
    • removedOutput schema / properties / generationsRemaining
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • removedOutput schema / properties / generationsUsed
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • addedOutput schema / properties / kind / const
      Added value: +"paid"
    • removedOutput schema / properties / kind / enum
      Removed value: -[
-  "demo",
-  "paid"
-]
    • changedOutput schema / required
      Previous value: -[
-  "kind"
-]New value: +[
+  "kind",
+  "creditBalance",
+  "frozen",
+  "recentSpendUsd"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's safety profile is clear. The description adds value by specifying the exact data fields returned, beyond what annotations provide.

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?

The description is a single sentence that is clear and front-loaded. Every word is necessary, and there is no wasted text.

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?

Given that an output schema exists, the description adequately explains what the tool returns. For a simple read operation with no parameters, this is complete.

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?

There are no parameters, and schema coverage is 100%. With zero parameters, the baseline is 4, and the description adds meaning by listing the return fields, which is not in the schema.

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 clearly states what the tool returns: credit balance, freeze state, and recent spend. It is specific and distinguishes from sibling tools like get_settings (which likely returns settings) and get_project (project details).

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?

No explicit guidance on when to use or when not to use alternatives. However, given the tool is a simple get with no parameters and sibling tools are for other resources, the usage context is somewhat implied but could be improved with direct statements.

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

All BetterPost toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose—project management, source and story handling, content generation, settings, and usage—with no overlapping functionality. The descriptions clearly delineate when to use each tool.

Naming Consistency5/5

All tools follow the consistent pattern 'betterpost_<verb>_<noun>', making the set predictable and easy to navigate. The naming convention is uniform throughout.

Tool Count5/5

With 23 tools, the server covers a comprehensive content generation workflow without being overwhelming. Each tool serves a necessary function, and the count feels well-scoped for the domain.

Completeness5/5

The tool surface covers the full lifecycle of project management, source acquisition, story curation, content generation/derivation, and settings configuration. There are no obvious gaps that would cause an agent to fail in typical use cases.

Resources