Skip to main content
Glama

AXAA — gift certificates for extreme activities

Карточка сертификата

get_certificate
Read-only

Один универсальный сертификат по type_id из list_certificates (0, 1, 2, 3 или 9). Если типа нет на витрине, вернётся ошибка.

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": {
      "type_id": "<type_id>"
    },
    "name": "get_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
type_idYesТип сертификата: 0, 1, 2, 3 или 9

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds the failure mode for an unavailable type, but says nothing about the shape or completeness of the returned certificate, which matters given there is no output schema.

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 short sentences, front-loaded with the operation and its keying parameter, with no filler. Re-listing the numeric values already present in the schema is slightly redundant but harmless.

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 single-parameter read tool with annotations, most of what an agent needs is present. The notable gap is the return payload: with no output schema and no mention of what fields a certificate card exposes, the agent cannot anticipate the response.

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?

Schema coverage is 100%, so the allowed values are already documented, and the description repeats them. However, it adds genuine meaning beyond the schema by identifying list_certificates as the authoritative source of valid type_id values and confirming that invalid types fail rather than return empty.

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 resource (a single certificate / 'карточка') retrieved by type_id, and names list_certificates as the source of that identifier, which separates it from the sibling list/discovery tools. It is clear but does not describe what the certificate record actually contains.

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?

It tells the agent where the required type_id comes from ('из list_certificates') and what happens when the type is unavailable on the storefront (an error), which is actionable invocation guidance. It stops short of explicit when-not-to-use or naming an alternative for bulk/listing needs.

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