Skip to main content
Glama

ai_modeling_usage

Read-only

List Studio credit transactions with pagination to review usage and credit history for an AI modeling account.

Instructions

List Studio credit transactions.

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

Input Schema

NameRequiredDescriptionDefault
page_numNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already state readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and openness are covered structurally. Beyond that the description adds nothing: no indication of ordering, whether results are paginated or bounded, how many transactions typically return, or whether the data is scoped to the authenticated account. For a list endpoint, the ordering/pagination behavior is the trait an agent most needs and it is absent.

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

Conciseness3/5

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

A single short sentence with no filler, so there is no verbosity problem. The issue is under-specification rather than conciseness: the sentence is front-loaded but does not carry enough information to be actionable on its own.

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?

With no output schema, no parameter documentation, and no annotation-adjacent detail in the text, the definition is thin for a paginated list tool. An agent lacks the scope (which account, which credit type), the ordering, and the pagination contract needed to call it confidently and interpret results.

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% for two parameters, so the description carries the burden of explaining page_num and page_size but says nothing about them. The schema only supplies types, defaults (1 and 20) and max 100, leaving unstated whether paging is 1-indexed with a hard cap and whether omitting them returns the first page. No compensation for the coverage gap.

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

Purpose3/5

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

The description gives a verb and a resource ("List" + "Studio credit transactions"), so the basic operation is identifiable. However, it does not distinguish this from closely related siblings such as ai_modeling_balance or ai_modeling_account_status, which likely surface overlapping credit/billing information. An agent cannot tell from the text alone which credit-related tool to choose.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. authentication), and no named alternative. The only implied usage is that this returns transaction history while something like ai_modeling_balance presumably returns a current total, but that distinction is left entirely 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