Skip to main content
Glama

Footalytics

get_account_credits

Remaining Footalytics credits on the connected account. Call this before a prediction when the user asks about their quota, or when a prediction call failed with insufficient_credits.

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_account_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does signal that this is a read of remaining balance on the connected account with no side effects implied. However, it says nothing about the response shape (units, whether a credit count or a breakdown), whether calling it is free, or rate limiting. For a zero-parameter read that is a modest but real gap rather than a serious one.

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 sentences, both earning their place: the first states what is returned, the second states when to call it. The resource definition is front-loaded ahead of the usage instructions, which is the right ordering.

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, the definition covers purpose, scope, and triggering conditions well enough to invoke correctly. The only shortfall is the absence of any note on what comes back (credit count format or whether it distinguishes plans), which matters because there is no output schema to lean on.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing any parameter discussion.

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 names a specific resource ('Remaining Footalytics credits') and scopes it to 'the connected account', which is distinct from every sibling (predictions, teams, fixtures, results). The verb is only implied ('Remaining'), so it is slightly less crisp than an explicit 'Retrieve remaining credits', but an agent can still tell instantly what this returns.

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 two concrete trigger conditions: the user asks about their quota before a prediction, or a prediction call failed with 'insufficient_credits'. That second trigger even ties it to the sibling get_match_prediction by name of error, so the agent has a deterministic routing rule rather than an inference.

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