Skip to main content
Glama

срезAI — Search API for AI agents

by ru.srezai
OverviewDiscussionsAdmin

Баланс, расход и лимиты / Balance, spending and limits

get_usage
Read-onlyIdempotent

Баланс, остаток суточной квоты, время сброса окна, burst-лимит и расход за последние сутки и неделю — по услугам, в кредитах. Ответ — компактный JSON (машиночитаемые поля первыми). verbose: true — тот же отчёт человеческим текстом вместе с полным прайс-листом.

Когда: вызов упал с [rate_limited] и надо понять, ждать секунды или до следующих суток; пользователь спрашивает про баланс и расходы; надо сверить свой лог вызовов с нашими списаниями; планируется большой батч. Возвращает: balance_credits, план, quota (used/limit/remaining/reset_min), burst, last24h (calls/credits/free и разбивка by_service) и week_credits. Без verbose прайс-листа в ответе нет — цены каждой услуги описаны у самой услуги, а здесь только то, что меняется от вызова к вызову. Тарификация: платите только за результат — ошибка и вызов, не принёсший ничего (пустая выдача, проверка без прочитанных источников), не списываются. Квота считает ВЫЗОВЫ, а не кредиты: 10 за 10 с и 200 в сутки на ключ. Цена: бесплатно, квоту и лимит запросов этот вызов не расходует — его можно звать без опасений.

Balance, remaining daily quota, window reset time, burst limit and spending for the last 24 hours and the last week, per service, in credits. The answer is compact JSON (machine-readable fields first). verbose: true gives the same report as human-readable text together with the full price list.

Use when: a call failed with [rate_limited] and you need to know whether to wait seconds or until tomorrow; the user asks about balance or spending; you need to reconcile your own call log with our charges; you are about to run a large batch. Returns: balance_credits, plan, quota (used/limit/remaining/reset_min), burst, last24h (calls/credits/free plus a by_service breakdown) and week_credits. Without verbose there is no price list: each service's price is described with that service, and this answer carries only what changes between calls. Billing: you pay for results only — an error, or a call that returned nothing (empty search results, a verification that read no sources), is not charged. The quota counts CALLS, not credits: 10 per 10 s and 200 per day per key. Cost: free — this call consumes neither quota nor rate limit, so call it freely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verboseNotrue — полный человекочитаемый отчёт с прайс-листом всех инструментов. По умолчанию компактный JSON без прайс-листа. / true — the full human-readable report with the price list of every tool. Default is compact JSON without the price list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / verbose
      Added value: +{
+  "description": "true — полный человекочитаемый отчёт с прайс-листом всех инструментов. По умолчанию компактный JSON без прайс-листа. / true — the full human-readable report with the price list of every tool. Default is compact JSON without the price list.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds valuable behavioral context: the call is free, consumes no quota or rate limit, and can be called freely. It also discloses billing semantics (only successful results are charged, quota counts calls not credits) and the response structure (compact JSON first, verbose for human-readable text). This goes well beyond the 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?

The description is longer than average but every section earns its place: purpose, when-to-use, return fields, billing semantics, and cost. It is front-loaded with the core purpose and uses clear section labels (Когда/Use when, Возвращает/Returns, Тарификация/Billing, Цена/Cost). The bilingual repetition adds length but serves a multilingual audience; still, it could be trimmed slightly without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only usage-reporting tool with one optional parameter and no output schema, the description is complete. It covers what the tool returns, when to use it, how billing works, and that it is free and non-consuming. The absence of an output schema is compensated by the explicit list of returned fields. Nothing an agent needs to call it correctly is missing.

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?

Schema description coverage is 100%, so the schema already documents the verbose parameter. The description adds meaning by explaining what verbose: true does (full human-readable report with price list) and what the default is (compact JSON without price list). It also clarifies the response fields, which helps the agent understand the parameter's effect. A small gap: it doesn't explicitly state that verbose is optional, but the schema already marks it as not required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it reports balance, remaining daily quota, window reset time, burst limit, and spending over the last 24 hours and week, per service, in credits. It clearly distinguishes itself from sibling tools like web_search or extract by focusing on account usage and billing data. The bilingual title and description reinforce the purpose without ambiguity.

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?

The description explicitly lists when to use the tool: after a rate_limited error, when the user asks about balance/spending, to reconcile call logs, or before a large batch. It also implies when not to use it by stating that prices are described with each service and that this tool only returns what changes between calls. This is strong contextual routing guidance.

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

All срезAI — Search API for AI agents toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources