Skip to main content
Glama
Sign In
dawg-mcp

dawg-mcp

by dawgswarm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

account_usage

Get the API key's account usage: minute/token consumption, limits, and active tariff plan, enabling informed decisions before running expensive operations.

Instructions

Get the current account usage and tariff plan for the configured API key.

Returns minute/token consumption, limits and the active plan so the agent can reason about remaining quota before running expensive operations.

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": "account_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the return values (minute/token consumption, limits, active plan) but does not mention potential caching, error states, or whether the data is instantaneous.

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?

Two sentences, each serving a purpose. The purpose is stated first, followed by the return value explanation. No unnecessary words.

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 tool with no output schema, the description completely covers the return values and the intended use case (quota reasoning). No gaps.

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 no parameters, so schema coverage is 100%. The description adds value by explaining the output structure (consumption, limits, plan), which is not in the schema. Baseline 4 is appropriate for zero parameters.

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 clearly states 'Get the current account usage and tariff plan', providing a specific verb and resource. It distinguishes itself from the sibling tools, which are all browser or scraping actions.

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?

The description suggests using the tool to check remaining quota before running expensive operations, giving clear context. It does not explicitly list when not to use or mention alternatives, but the guidance is sufficient for this simple tool.

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

Deploy Server

Other Tools