Skip to main content
Glama

Check NiceVois training allowance

get_training_account
Read-only

Check the connected account's free trainings, purchased training passes and subscription allowances before preparing a job. Any purchase link keeps checkout on this same account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
balanceYes
freeRunsYes
productsNo
signedInNo
accountUrlNo
freeTrainingNo
checkoutEnabledYes
freeRunMaxEpochsNo
freeRunMaxDurationSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 safety is covered. The description adds genuinely non-obvious behavior: returned purchase links keep checkout bound to this same account, which prevents an agent from assuming it should re-authenticate or switch accounts.

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 sentences, front-loaded with the resource being checked, with no filler. The trailing checkout sentence is slightly awkward in phrasing ('Any purchase link keeps checkout on this same account') but still earns its place as a caveat.

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?

An output schema exists and no parameters need documenting, so the remaining burden is small; the description covers what is read and the account-binding caveat. It does not mention behavior when no allowance remains, which would be a minor addition.

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 to disambiguate and the baseline is 4. The description correctly implies the account scope is derived from the connection rather than from an input argument.

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 uses a concrete verb plus resource ('Check the connected account's free trainings, purchased training passes and subscription allowances') and scopes it to one account. It implicitly separates this read-only allowance check from sibling job/quote tools via 'before preparing a job', though it never names an alternative explicitly.

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 states a clear use context: call this before preparing a job. There is no when-not guidance and no named alternative such as quote_training or get_training_requirements, but the triggering condition is explicit enough for an agent to sequence the call correctly.

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