Skip to main content
Glama

Axad

Plans and credit

upgrade_link
Read-only

Return a link on axad.ai where the learner can pick a plan, add a card for more free use, or buy credit; want says which. Returns the url and a short text.

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_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
wantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely useful context beyond that by disclosing the return payload ('the url and a short text'), which matters because no output schema exists. It is silent on link lifetime, whether repeated calls yield the same URL (annotations say idempotentHint=false, so this is a real open question), and that the returned URL points to an external domain.

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?

Two compact sentences with the action front-loaded and the return shape appended at the end where it belongs. The phrasing ('want says which') is slightly telegraphic, but nothing is wasted or redundant.

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 one-optional-parameter, no-output-schema tool, the description covers what it does, what the enum selects, and what comes back, which is close to the full surface an agent needs. Only the default behavior for an omitted 'want' and the link's longevity are unaddressed.

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 description coverage is 0%, and the schema only offers bare enum tokens, so the description must carry the meaning. It does partially: it expands 'card' into 'add a card for more free use' and maps the enum to the learner-facing outcomes. It does not say what happens when the optional parameter is left out, which is the main remaining semantic gap.

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 concrete verb and resource ('Return a link on axad.ai') and enumerates the three destinations the link can lead to, so the effect of calling it is unambiguous. It does not name or distinguish itself from any sibling, but none of the listed siblings plausibly overlap with generating an upgrade link, so the practical risk of confusion is low.

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?

Usage is implied by the three enumerated outcomes (pick a plan, add a card, buy credit) plus 'want says which', which tells the agent the parameter selects the destination. There is no explicit when-to-use/when-not framing, no mention of whether the caller should confirm with the learner first, and no guidance on what to do when 'want' is omitted.

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.