Skip to main content
Glama

check_credits

Read-onlyIdempotent

The paid Checks of a paying wallet, newest first, 50 a page with nextCursor: unused credits (status paid), a reading in flight or interrupted (status running: call check_analyze again with its target to resume) and the analyses already run (status used, with target and seal), to find a Check id you lost. The one check_* tool that reads by wallet, so the one that needs access, the Check access of this payer (check_access_challenge, then check_access).

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": {
      "payer": "<payer>",
      "access": "<access>"
    },
    "name": "check_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
payerYesThe paying wallet.
accessYesThe Check access of this payer from check_access (vca_...). Secret: it lists this payer's Checks.
cursorNonextCursor of the previous page, for the next 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / access / description
      Previous value: -"The Check access of this payer from check_access (vca_...). Secret: it reads and spends this payer's credits."New value: +"The Check access of this payer from check_access (vca_...). Secret: it lists this payer's Checks."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real behavioral context beyond them: ordering (newest first), page size (50), the three status values and what each means, and that it requires per-payer access. It stops short of describing the full response object or what happens at end-of-pagination beyond nextCursor, so it is strong but not exhaustive.

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?

All the content is relevant, but it is delivered as one long run-on sentence stitched with colons and parentheses, and the clause 'the one that needs access, the Check access of this payer' is redundant. The most important fact (what it lists) is front-loaded, which helps, but structure could be much tighter.

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?

With no output schema, the description carries the burden of explaining return values, and it does describe the status variants and their accompanying fields (target, seal) plus pagination. Missing pieces are minor, such as the exact shape of each listed Check or total counts. Overall it is adequate for a three-parameter read tool.

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?

Schema description coverage is 100%, so payer, access and cursor are already documented; the description mostly restates them ('the Check access of this payer', 'nextCursor'). It adds some framing about the access secret being per-payer, but nothing about cursor semantics that the schema lacks. Baseline 3 applies.

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 definition names the specific resource (the paid Checks of a paying wallet) and its scope, and explicitly differentiates itself from siblings: 'The one check_* tool that reads by wallet.' There is no clean leading verb (it opens with a noun phrase), so the purpose takes a moment to parse, but the identification is unambiguous once read.

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

Usage Guidelines5/5

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

It gives an explicit use case ('to find a Check id you lost'), the prerequisite chain ('check_access_challenge, then check_access'), and a concrete follow-up rule for in-flight items ('status running: call check_analyze again with its target to resume'). It also states which sibling this is not, by saying it is the only check_* tool that reads by wallet.

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