Skip to main content
Glama

Today's usage and limits

grok_usage
Read-onlyIdempotent

Check today's Grok Imagine usage, including image submissions, images generated or kept, and videos, to track progress against daily limits before generating more.

Instructions

Today's Grok Imagine usage (image submissions, images generated/kept, videos) against the daily limits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds genuinely new context the annotations lack: the temporal scope is limited to 'today' and the tally is broken down into specific counters (submissions, generated, kept, videos). It does not discuss refresh cadence or reset timing, which keeps it below 5.

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?

A single sentence with the scope ('today's') front-loaded and zero filler. Every clause carries information about what is measured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-argument, read-only usage snapshot with rich annotations there is little else needed. The description covers what is counted and the time window. Lacking an output schema, it could have sketched the returned fields or the limit/reset shape, which is the only real gap.

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. The description correctly does not invent argument semantics and instead spends its words on what the no-argument snapshot returns.

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?

The description names the specific resource (today's Grok Imagine usage) and enumerates the exact metrics counted: image submissions, images generated/kept, videos, measured against daily limits. That is far more precise than a name restatement and separates it from grok_set_limits and grok_status. It stops short of explicitly naming a sibling, keeping it at 4.

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

Usage Guidelines3/5

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

Reading the description makes the intended use (check today's consumption versus caps before submitting more work) reasonably obvious, especially next to grok_set_limits. However, there is no explicit when-to-use statement, no mention of the sibling that changes limits, and no prerequisites or exclusion guidance.

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