Skip to main content
Glama

ai_modeling_export_limit

Read-only

Checks your current Studio export allowance and account restrictions before exporting, so you can confirm limits and avoid failed export attempts.

Instructions

Read the current Studio export allowance and account restrictions before exporting.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds that the read covers allowances and restrictions, implying a gate that could block an export, but says nothing about what the response looks like, whether restrictions can be account-wide, or how to react if the allowance is zero.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single sentence with no filler, and the key intent ('before exporting') lands at the end of a short clause. It is efficient, though 'Studio' is never defined, which slightly undercuts immediate comprehension.

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

Completeness3/5

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

For a simple zero-parameter read there is little to explain, and annotations carry the safety profile. Still, with no output schema the description should hint at what the allowance/restriction result contains or what an agent should do with it, and that is absent.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool is 4. Schema coverage is 100% and empty, so no compensating detail is needed.

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 uses a specific verb ('Read') with two clearly named resources ('Studio export allowance' and 'account restrictions'), so an agent knows exactly what the call retrieves. It does not name a sibling tool it differs from, which keeps it short of a 5.

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?

The phrase 'before exporting' gives a genuine timing directive that tells the agent this is a pre-flight check. However, it offers no exclusions and does not distinguish this from plausible alternatives such as ai_modeling_account_status or ai_modeling_balance, leaving the choice to inference.

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