Skip to main content
Glama

kelpo_api_account

Read-onlyIdempotent

Read the account: credit balance (credits: balance, videos_5s_left, low, expires_next, buy_url, the 3 packs, message to relay), usage, limits, keys, storage and language (the language of API/MCP messages). Pass language="en" or "fr" to change the account language when the user asks. Kelpo never buys credits by itself: give the user buy_url. Arguments: {"query": {"language": ""}}

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / properties / language / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "fr",
      -      "en"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[A-Za-z]{2,3}([-_][A-Za-z]{2,4})?$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / query / properties / language / description
      Previous value: -"Optional: save the account language (\"fr\" or \"en\"). Messages, errors, questions and hints of the API, the MCP and the studio follow it."New value: +"Optional: the person's language. \"fr\" or \"en\" also becomes the language of the API/MCP messages; any other language is accepted, Kelpo's messages then stay in English and you translate them."
  2. First observed

TDQS

A3.5/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true and idempotentHint=true, but the description instructs passing language='en' or 'fr' to change the account language, which is a state mutation and contradicts the read-only annotation. This is an annotation contradiction, so transparency is misaligned even though other account details are disclosed.

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?

The description is front-loaded with 'Read the account' and then lists the returned fields efficiently. The trailing 'Arguments' JSON duplicates the schema and slightly adds noise, but otherwise it is dense and purposeful.

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

Completeness4/5

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

For a simple account-reading tool with no output schema, the description covers the main return areas, the language-change use case, and the credit-purchase policy. The annotation contradiction is a serious issue, but the descriptive information itself is largely complete for calling the tool.

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?

The description explains that the language parameter can change the account language and limits accepted values used for that change to 'en' or 'fr'. However, it doesn't explain the other accepted language values, the null option, or the fallback behavior that the schema description covers, leaving a gap when schema coverage is reported as 0%.

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 opens with a specific verb and resource: 'Read the account', and then enumerates the account data returned (credits, usage, limits, keys, storage, language). Sibling tools are about videos, projects, clients and editing, so this is clearly distinguishable.

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?

It gives concrete usage guidance: pass language='en' or 'fr' when the user asks to change account language, and never buy credits automatically—give the user buy_url instead. It doesn't spell out when not to use the tool, but the context is clear enough.

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