Skip to main content
Glama
Sign In

PromptGuard

by co.promptguard
OverviewDiscussionsAdmin

Get usage this month

promptguard_get_usage
Read-only

Show this billing month's PromptGuard usage against your plan: Requests used and remaining, the monthly limit, usage credit where the plan has one, and the days until it resets. Read-only. When to use: To check whether the account is close to its plan limit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "account": {
-        "type": "string"
-      },
-      "billedTokensThisMonth": {
-        "type": "integer"
-      },
-      "creditRemainingUsd": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "creditUsd": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "creditUsedUsd": {
-        "type": "number"
-      },
-      "daysRemaining": {
-        "type": "integer"
-      },
-      "kind": {
-        "const": "usage"
-      },
-      "monthlyLimit": {
-        "type": "integer"
-      },
-      "organization": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "plan": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "requestsRemaining": {
-        "type": "integer"
-      },
-      "requestsThisMonth": {
-        "type": "integer"
-      },
-      "status": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "usagePercentage": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "kind",
-      "account",
-      "requestsThisMonth",
-      "monthlyLimit",
-      "daysRemaining"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "error": {
-        "type": [
-          "string",
-          "object"
-        ]
-      },
-      "kind": {
-        "const": "error"
-      }
-    },
-    "required": [
-      "kind",
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "account": {
+        "type": "string"
+      },
+      "billedTokensThisMonth": {
+        "type": "integer"
+      },
+      "creditRemainingUsd": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "creditUsd": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "creditUsedUsd": {
+        "type": "number"
+      },
+      "daysRemaining": {
+        "type": "integer"
+      },
+      "kind": {
+        "const": "usage"
+      },
+      "monthlyLimit": {
+        "type": "integer"
+      },
+      "organizationId": {
+        "type": "string"
+      },
+      "plan": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "requestsRemaining": {
+        "type": "integer"
+      },
+      "requestsThisMonth": {
+        "type": "integer"
+      },
+      "status": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "usagePercentage": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "kind",
+      "account",
+      "requestsThisMonth",
+      "monthlyLimit",
+      "daysRemaining"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "kind": {
+        "const": "error"
+      }
+    },
+    "required": [
+      "kind",
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the trailing "Read-only." largely restates structured data. The description does add useful scope context (current billing month only, credit included where the plan has one, reset countdown), but since an output schema exists it needn't enumerate return values, leaving little beyond 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?

Two sentences, front-loaded with what is returned and followed by a compact when-to-use clause. No filler, no repetition of the title, and the enumeration is scannable.

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?

A zero-parameter, read-only snapshot tool with full annotation coverage and an output schema: nothing an agent needs to decide to call it is missing. Time scope (this billing month) and the read-only nature are both stated.

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 takes zero parameters, so the baseline is 4; there are no parameter semantics to clarify or obscure. The description correctly implies no filtering inputs are needed for the current-month snapshot.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Show this billing month's PromptGuard usage against your plan") and enumerates the exact contents: requests used/remaining, monthly limit, usage credit, days until reset. That makes it clearly distinguishable from siblings like promptguard_status or promptguard_get_fleet_status, though it never names an alternative to reinforce the distinction.

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?

An explicit "When to use" line scopes it to checking proximity to the plan limit, which is genuine selection guidance. It gives no when-not conditions and does not point to a sibling tool for adjacent questions (e.g. overall health via promptguard_status), so it stops short of full routing guidance.

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

All PromptGuard 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