Skip to main content
Glama
Sign In

SingIt x402

by app.singitai
OverviewDiscussionsAdmin

Get allowance

get_allowance
Read-onlyIdempotent

How much you can still spend right now, before you pay: your API key's remaining today and per-request cap, and your wallet allowance's remaining today, per-purchase cap and approval on Base or Solana, each with spendableNowUsd and bindingLimit (the limit that would refuse a larger call). Read-only: it cannot change a limit. Free, but needs your API key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds value by making the safety claim concrete ('it cannot change a limit') and by disclosing the auth requirement ('needs your API key') and that calls are free. It also defines the semantics of bindingLimit, which is genuinely useful behavioral context rather than a restatement of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence that puts the core answer ('how much you can still spend') first and then enumerates the components. The middle clause is dense and slightly run-on, packing two limit families plus two chains into one breath, but no sentence is filler.

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 the return shape, and it does so by naming the fields and their meaning for both the API-key and wallet halves. It is nearly complete for a zero-argument read tool; only edge behavior (e.g. what is returned when no wallet or approval is configured) is left unstated.

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 nothing for the description to disambiguate and the baseline is 4. The description instead spends its words on output semantics (spendableNowUsd, bindingLimit), which is a reasonable substitute given the absence of parameters.

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 states a specific resource and measurement: remaining spendable amount now, broken into API-key limits (today, per-request cap) and wallet allowance (today, per-purchase cap, approval on Base or Solana). That is far more precise than the name alone. It does not, however, differentiate itself from close siblings like get_limits or get_balance, so an agent must infer the split.

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?

Usage is only implied by the phrase 'before you pay' and 'How much you can still spend right now', which suggests a pre-flight check. There is no explicit when-to-use statement, no exclusion, and no pointer to get_limits or get_balance as the alternative for a related question.

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

All SingIt x402 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources