Skip to main content
Glama

checkers.fr — entreprises françaises

Crédits restants

credits_restants
Read-onlyIdempotent

Indique les crédits de l’abonnement (inclus et consommés ce mois-ci) et les crédits à l’unité restants sur le compte de la clé utilisée. Gratuit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description still adds real value beyond them: it enumerates exactly which two balances are reported and, critically, states the call is free — information the annotations do not convey. It does not say what happens on missing/invalid key, which keeps it below a 5.

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?

Two short sentences, front-loaded with the resource and its two components, ending with the cost note. No filler, no 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 zero-parameter, read-only, no-output-schema tool, the description covers what is measured and the cost profile, which is enough to call it correctly. It stops short of describing the shape/units of the returned figures, but with no output schema that is a minor gap for a balance check.

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, which is the baseline-4 case. The description correctly adds no parameter narrative, and instead clarifies that scoping is implicit via the API key used, which is the one semantic point an agent needs.

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?

Uses a specific verb ('Indique') with a clearly bounded resource: subscription credits (included and consumed this month) plus remaining pay-per-use credits, scoped to the account tied to the key in use. That is far more precise than the tool name alone. It does not name a sibling, but the sibling set (company/document search) is a different domain, so differentiation is implicitly obvious rather than stated.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The closing 'Gratuit' implies a sensible pattern (call this to inspect balance before spending credits), but the agent must infer that. Minimum-viable guidance only.

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