Skip to main content
Glama
scamverifyai

ScamVerify

get_usage

Read-onlyIdempotent

Check your current API usage quota and rate limits across phone, URL, text, email, and document verification channels to monitor consumption against billing period allocations.

Instructions

Check your current API usage quota and rate limits for the billing period. Shows per-channel usage (phone, URL, text, email, document) with limits and remaining counts. QR lookups consume URL quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool 'get_usage' is registered directly in src/index.ts using the 'server.tool' method. It uses the 'apiGet' helper to fetch data from the '/api/v1/usage' endpoint and returns it via 'jsonResult'.
    // 9. get_usage
    server.tool(
      'get_usage',
      'Check your current API usage quota and rate limits for the billing period. Shows per-channel usage (phone, URL, text, email, document) with limits and remaining counts. QR lookups consume URL quota.',
      {},
      {
        title: 'Get Usage & Quota',
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
      async () => {
        try {
          const data = await apiGet('/api/v1/usage');
          return jsonResult(data);
        } catch (err) {
          return errorResult(err instanceof Error ? err.message : 'Failed to get usage');
        }
      },
    );
Behavior4/5

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

Annotations already declare readOnly/idempotent/safe properties, lowering the burden. The description adds valuable context: the 'billing period' time scope, specific channel breakdown mapping to sibling tools, and the critical quota consumption rule that QR lookups count against URL quota—behavioral details not present in structured data.

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?

Three sentences with zero waste: first establishes purpose, second details the channel-specific return structure, third provides critical QR quota behavior. Front-loaded with action verb and appropriately sized.

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?

No output schema exists, but the description compensates by explaining return content ('per-channel usage with limits and remaining counts'). Given zero parameters and read-only nature, this is sufficiently complete, though it could specify the exact structure or format of the returned data.

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?

Input schema contains zero parameters (empty object). Per calibration rules, zero parameters establishes a baseline score of 4, which is appropriate here as there are no parameter semantics to elaborate upon.

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 uses specific verb 'Check' with clear resource 'API usage quota and rate limits' and scope 'billing period'. It implicitly distinguishes from check_* siblings by focusing on quota metrics rather than validation.

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?

Provides implied usage context by mapping channels (phone, URL, text, email, document) to the sibling tools. Includes specific behavioral note that 'QR lookups consume URL quota' which guides usage of check_qr, but lacks explicit when-to-use/when-not-to-use guidance versus alternatives like get_status.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scamverifyai/scamverify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server