Skip to main content
Glama

SwapHunt crypto market context

get_quota

Read-onlyIdempotent

Free. Use when the user asks how many free SwapHunt calls are left today. Returns calls left (market tools; pm_fees does not count), when they reset (00:00 UTC) and how to get more. Ex: no parameters

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description need not repeat safety traits. It adds useful quota semantics: free calls, reset at 00:00 UTC, market-tool counting, pm_fees exclusion, and how to get more. It does not describe exact output keys or error behavior, but the behavioral view is strong overall.

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?

Three tight sentences with little waste, front-loading the free-call nature and then the usage trigger. 'Ex: no parameters' is slightly redundant against an empty schema, but it is not harmful.

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 simple zero-parameter quota check with annotations and no output schema, the description covers the trigger, returned information, reset timing, counting rule, and how to get more. Nothing material is missing for correct invocation.

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 has zero parameters and the schema is empty, so no parameter semantics are required. The description's 'Ex: no parameters' confirms the call pattern, though it is largely redundant with the schema. This meets the zero-parameter baseline of 4.

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?

Explicitly states that the tool reports remaining free SwapHunt calls for today, names the returned information, and distinguishes pm_fees from counted market tools. This gives a specific verb, resource, and scope that an agent can match without inspecting the schema.

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

Usage Guidelines4/5

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

Provides a direct trigger: use it when the user asks how many free SwapHunt calls are left today. It also notes the pm_fees exclusion, though it does not spell out broader when-not-to-use cases or alternative quota tools.

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.