Skip to main content
Glama

Get one exam voucher

get_voucher
Read-onlyIdempotent

Full details for one exam voucher by exam code: price, validity, delivery time, exam provider, regions and facts.

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": {
      "exam_code": "<exam_code>"
    },
    "name": "get_voucher"
  }
}

Input Schema

NameRequiredDescriptionDefault
exam_codeYesExam code, e.g. AZ-900

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully provided. The description adds useful value by naming the returned fields, which matters because no output schema exists, but it says nothing about behavior on an unknown or invalid exam code (error vs. empty result).

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?

One sentence with no filler, front-loading the action and resource before the enumerated payload. Every clause earns its place and there is no redundant restatement of the title.

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 read tool with no output schema, listing the returned fields plus annotations covering safety and world scope covers nearly everything an agent needs. The only gap is unspecified behavior for a missing/invalid exam code.

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% and the single parameter has a concrete example ('AZ-900'), so the baseline is 3. The description adds a bit of meaning by tying the parameter to the returned record ('by exam code'), confirming it is an exact identifier rather than a free-text query.

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 retrieval action on a single resource ('Full details for one exam voucher') and scopes it by exam code, then enumerates the data returned (price, validity, delivery time, provider, regions, facts). This clearly separates it from the plural sibling search_vouchers, though it does not name any sibling explicitly.

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 only implied: the phrase 'by exam code' signals this is for a single already-known exam, which implicitly contrasts with a search or price-comparison tool. There is no explicit when-to-use/when-not statement or named alternative such as search_vouchers or compare_price for discovery-style lookups.

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