Skip to main content
Glama
AgentExtract MCP

AgentExtract MCP

check_balance

Check remaining AgentExtract credit balance and account status with an API key to verify available credits before running web extraction tasks.

Instructions

Checks your remaining AgentExtract credit balance and account status.

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

Input Schema

NameRequiredDescriptionDefault
apiKeyNoThe API key to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations have been supplied, so the description carries the full burden of disclosing behavior, and it discloses very little. It implies a read-only check but never says what happens with a missing, default or invalid apiKey, whether the call costs credit, or whether authentication errors surface as results or exceptions.

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?

One sentence, front-loaded with the action and its resource, with no filler or hedging. Nothing in it is wasted, and the most useful information leads.

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 low-complexity, single-parameter read tool whose schema is fully documented, the description covers what it does and what it conceptually returns (balance and account status). The remaining gaps are minor: error behavior and the apiKey fallback are undocumented, and there is no output schema to fall back on.

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 single apiKey parameter reaches 100% schema coverage, so the schema fully documents it and the baseline of 3 applies. The description adds no meaning beyond the schema: it doesn't say whether apiKey defaults to a configured credential, which matters because the field is not required.

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 verb and resource: it 'Checks your remaining AgentExtract credit balance and account status.' That verb/resource pair means an agent can tell it apart from the extraction siblings (extract_clean_markdown, extract_tables). It doesn't explicitly say what it is not, though, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description never says when an agent should call this tool rather than do something else: whether to check it before an extraction, only when extraction fails, or on a schedule. It has neither alternatives nor exclusions, so the agent has to infer the trigger condition entirely.

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