Skip to main content
Glama

Kubeez

open_pricing

Read-onlyIdempotent

Scope: none. Deep-link to the Kubeez pricing / credit top-up page, with the user's CURRENT balance surfaced in the summary so the agent can phrase the suggestion without an extra get_balance call. Use when a generation fails with insufficient_credits, when estimate shows a cost > balance, or when the user explicitly asks to buy more. Returns { url, summary, current_balance }. Phrase to the user e.g. 'You have N credits, this run needs M — top up at '.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds that balance is pre-fetched into the summary and that it returns `{ url, summary, current_balance }`, but that return detail duplicates the output schema. Nothing about rate limits or what happens on the linked page.

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 purpose, then triggers, then return shape, then a phrasing template — a good information order. It is dense but every clause carries content; the only near-waste is the cryptic 'Scope: none.' opener and the redundant phrasing example.

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-arg deeplink tool with annotations and an output schema, the description covers when to call it, what it returns, and even how to phrase the result to the user. Nothing an agent needs in order to select or invoke 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 parameters, so the baseline of 4 applies. The 'Scope: none.' prefix signals there is nothing to pass, which is mildly helpful but not explanatory in any deeper sense.

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 action (deep-link to the Kubeez pricing / credit top-up page) plus a distinguishing behavior (surfaces the CURRENT balance in the summary). This separates it clearly from get_balance and estimate, which appear in the sibling list.

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 three concrete triggers: generation fails with `insufficient_credits`, `estimate` cost exceeds balance, or the user explicitly asks to buy more. It also notes the alternative (calling `get_balance` first) is unnecessary, which is explicit routing guidance.

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