Skip to main content
Glama

DeFade — Multi-Chain Memecoin Analyzer

by org.defade
OverviewDiscussionsAdmin

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.

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 EVM calls, listed in heavyOnEvm with heavyCost.
usageNotoday, total, thisPeriod, remainingThisPeriod, periodResetsAt.
limitsNoperMinute, perDay, perMonth; perMonth is null on grandfathered keys.
creditsNoOverage: balance, overageEnabled, costPerRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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."
  3. 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"
+]
  4. 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"
+}
  5. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful scope context: it operates on the calling key, takes no arguments, and is orthogonal to the token-address tools. It stops short of stating anything about the returned allowance window beyond 'monthly', but that is minor given 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.

Conciseness5/5

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

Three tight sentences, front-loaded with the purpose and followed by usage triggers and an exclusion. No filler.

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?

An output schema exists, so return values need not be described. Purpose, trigger conditions, scope boundary, and argument count are all covered — nothing an agent needs to call this 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?

Zero parameters, so the baseline is 4. The description reinforces this with 'Takes no arguments', matching the empty schema with additionalProperties=false.

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?

States a specific verb and resource ('Report the calling API key's plan, rate limits and remaining monthly allowance') and explicitly scopes it to the key rather than a token, which cleanly separates it from every sibling tool that takes an address.

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?

Gives two concrete trigger conditions ('when a call fails on quota', 'when the user asks what their DeFade plan includes') plus an explicit exclusion ('Not for anything about a token'). The agent can route without inference.

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

All DeFade — Multi-Chain Memecoin Analyzer 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