Skip to main content
Glama

AceRound AI Interview Copilot

get_purchase_link

Read-only

Create a purchase link for a plan for the user to open in a browser: after signing in to AceRound, checkout for that plan opens automatically, priced for the user's country. Product ids come from list_plans.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productId": "<productId>"
    },
    "name": "get_purchase_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesA product id from list_plans

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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. The description adds genuinely new behavioral context: the link opens in a browser, requires AceRound sign-in, auto-launches checkout, and applies country-based pricing. Remaining gaps are link lifetime/expiry and whether repeated calls return the same 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?

A single front-loaded sentence with a colon that expands into the useful behavior detail. Nothing is wasted, and the most important clause (what the link does) comes first.

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-parameter tool with no output schema and full annotation coverage, the description covers purpose, prerequisite, and post-invocation behavior adequately. It stops short of saying what is actually returned (a URL string) or how errors surface when an invalid productId is supplied.

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 productId parameter is fully documented in the schema as coming from list_plans. The description's 'Product ids come from list_plans' restates the schema rather than adding format, validity, or error semantics, 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?

States a specific verb and resource ('Create a purchase link for a plan') and immediately explains what the resulting link does. It is clearly not a listing or checkout tool, and it points at list_plans as the source of ids, though it does not explicitly distinguish itself from other purchase-adjacent siblings such as activate_subscription_card.

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?

Gives a concrete prerequisite chain — call list_plans first to obtain productId — and describes the end-to-end user flow after the link is opened. It lacks any explicit when-not or alternative-selection guidance, so an agent must infer that this is the right tool whenever a shareable checkout URL is needed.

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