Skip to main content
Glama

Get Klynx plan allowance

klynx_get_balance
Read-onlyIdempotent

Use this when the user asks how many Klynx posts or AI features they have left, or before klynx_write_captions or klynx_create_post_pack when the allowance may be low. Returns the plan of the connected Klynx account, the posts and AI features remaining in its allowance, and the period they cover (this month, or today on a daily allowance). Free, takes no inputs and changes nothing. It cannot change the plan; plans are managed in the user's Klynx account.

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": "klynx_get_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
plan_nameYesThe Klynx plan, for example Free or Starter.
posts_periodYesmonth for monthly plans; today for daily allowances.
posts_remainingYesPosts left in the plan allowance, or null when there is no limit.
ai_features_remainingYesAI features (photo enhancements and AI text overlays) left in the plan allowance, or null when there is no limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds context beyond the annotations: the call is free, takes no inputs, changes nothing, and cannot modify the plan. 'Changes nothing' partly restates readOnlyHint and naming the returned fields overlaps the output schema, but the cost and plan-management boundary are genuine additions.

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 the use case, then return contents, then limits. Well structured, though the 'Free, takes no inputs and changes nothing' clause slightly duplicates annotation and schema information that could be trimmed.

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-argument read tool with an output schema and full annotation coverage, this is complete: it explains what comes back, the period semantics (monthly vs daily), and the read-only boundary. Nothing needed to call it correctly 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 parameters, so the baseline is 4. The description's 'takes no inputs' correctly confirms this and leaves no ambiguity about whether a hidden argument is required.

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 (Klynx plan allowance) and exactly what it returns: the plan, posts and AI features remaining, and the coverage period. It also distinguishes itself from siblings by naming klynx_write_captions and klynx_create_post_pack as the write operations it precedes.

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

Usage Guidelines5/5

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

Gives explicit triggers (user asks how many posts/AI features are left; before writing captions or creating a post pack when allowance may be low) and an explicit exclusion (it cannot change the plan; plans are managed in the Klynx account). No inference needed to decide when to call it.

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