Skip to main content
Glama

AXAA — gift certificates for extreme activities

Универсальные сертификаты

list_certificates
Read-only

Универсальные подарочные сертификаты AXAA, которые сейчас продаются на сайте: Маленькое, Большое, Двойное, Абсолютное и Персональное Счастье.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds essentially nothing about behavior beyond restating that these are gift certificates on sale. It does not state that the tool returns all of them, in what form, or whether ordering/pricing information is included.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no waste, which is good, but it is not front-loaded with an action verb and reads as a catalog blurb rather than a tool definition. Brevity here comes at the cost of stating the actual operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only listing tool with no output schema, the description is close to adequate in that it names exactly which certificates exist on the site. It falls short of telling an agent that calling it returns that list, and the Russian-only text assumes the caller reads Russian while the tool and sibling names are English.

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; baseline 4 applies. The enumeration of certificate types arguably acts as lightweight semantic framing of the result set, though it is not a parameter.

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

Purpose3/5

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

The description is a noun phrase naming the resource ('Универсальные подарочные сертификаты AXAA, которые сейчас продаются на сайте') rather than stating the action, so the listing behavior is only inferred from the tool name list_certificates. It does identify the specific resource and enumerate the five certificate varieties, which helps distinguish it from get_certificate, but it never says the tool returns the set of currently purchasable certificates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus get_certificate or create_order, and no mention of prerequisites or exclusions. The phrase 'которые сейчас продаются на сайте' implies only currently-sold certificates are covered, but that constraint is not framed as usage 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