Skip to main content
Glama

Compare Plans

upgrade_account
Read-onlyIdempotent

Show HalalGen's plans (prices and monthly credits) with a link to the pricing page. Works without signing in.

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

Input Schema

NameRequiredDescriptionDefault
planNoPlan to highlight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld=false, so the bar is lower. The description adds real value beyond them by disclosing the no-auth requirement and previewing the returned content (prices, monthly credits, pricing-page link).

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?

Two short sentences, zero filler, with the core capability front-loaded and the auth caveat second. Every phrase earns its place.

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?

With one optional parameter, an output-free schema, and rich annotations, the description is nearly sufficient: it covers what is shown, the no-auth condition, and the external link. The only gap is not clarifying that no actual upgrade occurs, which matters given the tool name.

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?

Schema coverage is 100%, and the single 'plan' parameter already carries an enum and a description ('Plan to highlight'). The prose adds nothing about how the highlighted plan changes the output, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it shows plans with prices, monthly credits, and a pricing-page link, and clarifies it is informational rather than a mutation. It does not address the mismatch with the tool name 'upgrade_account' or distinguish itself from siblings like estimate_cost or get_balance, which leaves some ambiguity about the upgrade framing.

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?

'Works without signing in' gives one useful usage condition (no auth needed). However, it never says when to use this versus estimate_cost or get_balance, nor explicitly that calling it does NOT perform an upgrade — a meaningful exclusion for a tool named 'upgrade_account'.

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