Skip to main content
Glama

AceRound AI Interview Copilot

redeem_credits

Destructive

Convert all account credits into interview minutes and mock interviews: every 200 credits become 60 minutes and 2 mock interviews. All credits are converted at once and any remainder below 200 is cleared. Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (Requires the user's sign-in with scope account:write.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the conversion is all-or-nothing, that any remainder under 200 is forfeited, that the operation may fall through to creating a payment, and that account:write scope sign-in is required. These are exactly the cost and destruction details an agent needs before calling a destructive, non-open-world mutation.

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 conversion rule is front-loaded in the first sentence, followed by the forfeiture rule and the consent/auth requirements, with no filler. The auth note in parentheses at the end is slightly buried but still earns its place.

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?

With no parameters and no output schema, the description carries the full load and does so: conversion math, all-at-once behavior, remainder loss, possible payment creation, and auth scope are all covered. An agent has everything needed to decide and warn the user before invoking.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema is self-explanatory. Baseline for a parameterless tool applies.

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 verb and resource (convert credits into interview minutes and mock interviews) plus the exact conversion rate, which lets an agent separate it from siblings like redeem_gift_code or buy_auto_apply_credits without opening any schema.

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?

It gives a real precondition — tell the user the cost and get agreement first — and implies usage by saying all credits are converted at once. However, it never states when to choose this over the credit-purchasing or gift-code siblings, leaving alternative routing to inference.

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