Skip to main content
Glama

Change daily limits

grok_set_limits
Idempotent

Set daily caps for Grok videos, image submissions, and batch jobs; omitted limits remain unchanged.

Instructions

Change the daily Grok quota guard (only when the user asked for it). Omitted values stay as they are.

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

Input Schema

NameRequiredDescriptionDefault
confirm_overNo
max_jobs_per_batchNo
max_videos_per_dayNo
max_image_submissions_per_dayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the mutation as idempotent, non-destructive, and closed-world, so the description does not need to repeat safety basics. It adds the important partial-update behavior ('omitted values stay as they are'), but does not cover validation, authorization, or what happens when limits are lowered or raised.

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 a single tight sentence with the key condition and the partial-update rule front-loaded. There is no filler or repetition.

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

Completeness2/5

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

For a four-parameter mutation tool with no parameter descriptions and no output schema, the definition is too sparse. Annotations cover safety traits, but an agent still lacks enough detail about the parameters and the effects of changing daily limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It only explains that omitted values remain unchanged, and never clarifies what confirm_over means or how the three max_* limits should be interpreted.

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 states a specific verb (Change) and resource (daily Grok quota guard), making the tool's purpose clear. It does not explicitly differentiate itself from siblings such as grok_settings or grok_usage, but the limits focus is reasonably distinct.

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?

It gives a useful condition ('only when the user asked for it'), but does not name alternatives, explain when not to use it, or relate it to grok_settings/grok_status. The guidance is implied rather than fully explicit.

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