Skip to main content
Glama

ai_modeling_account_status

Read-only

Check your Tripo Studio session status and remaining credits without exposing credentials.

Instructions

Check your Studio session and credits. Returns no credentials.

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

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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioural fact beyond them: 'Returns no credentials,' which tells the agent this is safe to surface. It says nothing about whether the call can fail on an expired session, what the credit figure represents, or any rate limiting.

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?

Two short sentences with the purpose front-loaded and no filler. The second sentence is terse to the point of being cryptic ('Returns no credentials'), but it is short and does add a distinct fact rather than repeating the first.

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 zero-parameter read-only status tool with annotations and no output schema, the definition is minimally sufficient. However, with no output schema, an agent has no idea what the response contains (credit balance, session validity, expiry) beyond the negative statement about credentials, which leaves a real gap for a tool whose whole value is its return payload.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter language is present.

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 a specific verb and resource: 'Check your Studio session and credits.' An agent can immediately tell this is a read-only status probe rather than an action tool. It stops short of distinguishing itself from near-neighbours such as auth_status or balance, leaving some ambiguity about scope overlap.

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?

Usage is only implied: 'Check your Studio session and credits' suggests calling it when you need session or credit information, but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisites or call-order guidance is given.

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