Skip to main content
Glama

DeFade — Multi-Chain Memecoin Analyzer

API usage

get_usage
Read-onlyIdempotent

Report the calling API key's plan, rate limits and how much of its monthly allowance is left. Takes no arguments. Use it when a call fails on quota, or when the user asks what their DeFade plan includes. Not for anything about a token — every other tool takes an address; this one reports on the key itself.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tierNoThe tier this key is on. web_mcp is the connector key included with a DeFade Pro web subscription; its allowance is the plan's monthly scans, reported in plan/limits.perMonth.
unitsNoHow metering works: one request is one unit except the heaviest calls, listed in heavyOnEvm with heavyCost and in heavyOnSolana with heavyCostOnSolana.
usageNotoday, total, thisPeriod, remainingThisPeriod, periodResetsAt.
limitsNoperMinute, perDay, perMonth: the monthly allowance in units, or for the Pro connector key the web plan's monthly scans.
creditsNoOverage: balance, overageEnabled, costPerRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / limits / description
      Previous value: -"perMinute, perDay, perMonth; perMonth is null on grandfathered keys."New value: +"perMinute, perDay, perMonth: the monthly allowance in units, or for the Pro connector key the web plan's monthly scans."
  2. Changed1 schema field changed
    • changedOutput schema / properties / units / description
      Previous value: -"How metering works: one request is one unit except the heaviest EVM calls, listed in heavyOnEvm with heavyCost."New value: +"How metering works: one request is one unit except the heaviest calls, listed in heavyOnEvm with heavyCost and in heavyOnSolana with heavyCostOnSolana."
  3. Changed1 schema field changed
    • changedOutput schema / properties / units / description
      Previous value: -"How metering works: one request is one unit except the heaviest EVM modules, listed in heavyOnEvm with heavyCost."New value: +"How metering works: one request is one unit except the heaviest EVM calls, listed in heavyOnEvm with heavyCost."
  4. Changed1 schema field changed
    • changedOutput schema / properties / tier / description
      Previous value: -"The tier this key is on."New value: +"The tier this key is on. web_mcp is the connector key included with a DeFade Pro web subscription; its allowance is the plan's monthly scans, reported in plan/limits.perMonth."
  5. Changed5 schema fields changed
    • changedOutput schema / properties / credits / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / limits / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / tier / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / units / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / usage / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "credits": {
      +      "additionalProperties": true,
      +      "description": "Overage: balance, overageEnabled, costPerRequest.",
      +      "type": "object"
      +    },
      +    "limits": {
      +      "additionalProperties": true,
      +      "description": "perMinute, perDay, perMonth; perMonth is null on grandfathered keys.",
      +      "type": "object"
      +    },
      +    "tier": {
      +      "description": "The tier this key is on.",
      +      "type": "string"
      +    },
      +    "units": {
      +      "additionalProperties": true,
      +      "description": "How metering works: one request is one unit except the heaviest EVM modules, listed in heavyOnEvm with heavyCost.",
      +      "type": "object"
      +    },
      +    "usage": {
      +      "additionalProperties": true,
      +      "description": "today, total, thisPeriod, remainingThisPeriod, periodResetsAt.",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  7. Added

TDQS

A4.7/5.0
Behavior4/5

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

While annotations cover safety, the description adds valuable context by detailing *what* the tool reports (plan, limits, allowance) and the fundamental behavioral constraint that it operates on the 'key itself,' not related data points. This is critical for behavioral clarity.

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?

The description is highly efficient. It follows a logical flow: function -> usage scenarios -> constraints/differentiation, with no wasted language.

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?

Given that the tool takes no arguments and has rich contextual guidance on its purpose and limitations, the definition is extremely complete for enabling correct selection and 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?

Since there are zero parameters, the baseline score is 4. The description does not need to add semantic meaning beyond the schema, but it confirms the tool operates on the implicit 'calling API key'.

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 verbs and resources ('Report the calling API key's plan, rate limits') and is immediately clear about its function. The tool's purpose is unambiguous.

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?

It provides explicit use cases ('Use it when a call fails on quota, or when the user asks what their DeFade plan includes'). Crucially, it delineates boundaries by stating what it is 'Not for' (tokens), which is highly effective for agent routing.

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