Skip to main content
Glama

list_training_credit_codes

Read-onlyIdempotent

Look up prepaid training-credit balances and remaining amounts. Search by tracking identifier or credit code to see credits used, total, and expiration behavior.

Instructions

Find prepaid training-credit balances and how much is left on them.

    Different from a promo code: a promo code discounts a purchase, a training-credit
    code carries a BALANCE that is spent down. `credits_used` against `credits_total`
    says how much is left.

    `tracking_identifier` is the customer-side reference, usually a PO or contract
    number, and is the field to search when someone asks about "their credits".

    `expire_content` says whether access bought with the credits expires when the
    code does - a separate question from the balance running out.

    Requires `CSA_SKILLJAR_V1_API_KEY`, a separate credential from the v2 client.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
page_sizeNo
filter_tracking_identifierNo
filter_training_credit_codeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
pageNo
rowsYes
totalNo
has_moreNo
next_pageNo
Install Server

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description adds substantial behavioral detail: the spend-down balance model, the meaning of credits_used versus credits_total, how expire_content differs from balance depletion, and the separate CSA_SKILLJAR_V1_API_KEY credential requirement. No contradiction with annotations.

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?

The description is front-loaded with the core purpose, and every subsequent sentence adds distinct value: the promo-code contrast, balance interpretation, customer reference guidance, expiry semantics, and credential requirement. It is detailed without being padded.

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

Completeness5/5

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

Given that an output schema exists and annotations cover read-only/idempotent safety, the description supplies what an agent needs to use the tool correctly: the required credential, the distinction from promo codes, and the key field to search. Nothing material is missing for a list operation.

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?

The input schema has no parameter descriptions, so the description must compensate. It explains filter_tracking_identifier thoroughly and clarifies related output concepts, but page, page_size, and filter_training_credit_code receive no added semantics beyond their titles. This is useful but incomplete for a 0% schema coverage case.

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

Purpose5/5

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

The description opens with a specific action and resource: 'Find prepaid training-credit balances and how much is left on them.' It also explicitly distinguishes training-credit codes from promo codes, which differentiates it from sibling tools like list_promo_codes.

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 gives clear usage context: use this for training-credit balances rather than promo codes, and search by tracking_identifier when a customer asks about 'their credits.' It does not explicitly name an alternative tool or state 'do not use for promo codes,' but the contrast is strong enough to guide an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server