Skip to main content
Glama

XCROP X (Twitter) data

Get credit balance

get_credits
Read-only

Credits left on your XCROP key: plan allowance, used, remaining and top-up balance. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the call itself is 'Free' and does not consume credits, which matters for a tool whose subject is credit consumption. It says nothing about refresh cadence, expiry of top-up balances, or what is returned at zero balance.

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?

A single dense sentence with no filler: the resource, the four returned components, and the cost signal are all front-loaded. Every clause earns its place, and nothing is repeated from structured fields.

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 zero parameters and no output schema, the description carries the burden of describing the response, and it does so by naming the four balance components. What is missing is narrower context — whether allowances reset, whether top-ups expire, and what the response looks like at zero. For a trivial read-only getter this is close to sufficient.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste space restating an empty schema, which is appropriate.

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 the concrete resource — the credit balance on the user's XCROP key — and enumerates what the balance comprises: plan allowance, used, remaining, and top-up balance. It is unambiguously distinct from the sibling endpoints, which all read social-graph or tweet data. A verb is only implied rather than stated ('Credits left on...'), which keeps it a notch below a fully explicit verb+resource phrasing.

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?

There is no when-to-use guidance: nothing says to call this before other operations, how often to check, or what to do when the balance reaches zero. The only usage-adjacent signal is 'Free', which describes cost rather than context. With no alternatives to weigh here, the gap is smaller than for a competing tool, but no guidance is present.

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