Skip to main content
Glama

ai_modeling_export_lite

Record lightweight export authorization and credit counting for Studio projects without creating files; reuse request_id for safe retries and avoid blind retries after outcome_unknown.

Instructions

record lightweight export authorization/counting; creates no file (use local-convert). Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_export_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description adds genuinely non-redundant behavior: idempotency via request_id (reuse returns the original job), conflict on changed input, no file side effect, account binding, and a warning against blind retry after outcome_unknown. It does not explain what an authorization record actually persists or how to resolve an outcome_unknown state, which keeps it below a 5.

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?

The description is compact, front-loaded with the core purpose, and every clause carries information (no-file note, account binding, idempotency, conflict, retry warning). The phrase "record lightweight export authorization/counting" is slightly compressed jargon, but no sentence is wasted.

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 nested-object, three-required-parameter mutation with no output schema, the description covers the risky semantics (idempotency, retry safety) that an agent most needs. It leaves the credit budget parameter and the export parameter block entirely undocumented, and does not describe what the recorded job/response looks like, so it is adequate but incomplete.

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% with three top-level required parameters and a nested parameters object containing format, project_id, operator_id and public_model. The description only illuminates request_id (stable, reused for idempotency); max_estimated_credits and the entire nested parameter block, including format enums and public_model, receive no explanation.

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 gives a concrete verb plus resource: it records a lightweight export authorization/counting entry rather than producing an artifact, and it explicitly says "creates no file (use local-convert)". That distinguishes it from a file-producing convert path, though it does not disambiguate it from export siblings such as ai_modeling_export_batch or ai_modeling_model_export.

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?

It tells the agent when not to use it (any tool that actually produces a file should go to local-convert) and gives a hard retry rule for the outcome_unknown state. It stops short of stating the entry conditions or which sibling to use for related export variants, so alternatives beyond local-convert are left implicit.

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