Skip to main content
Glama

ai_modeling_project_get

Read-only

Retrieve details for a Tripo Studio project, optionally scoped to a specific operator, to inspect project state and structure.

Instructions

Inspect a Studio project, optionally at a selected operator.

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": {
      "project_id": "<project_id>"
    },
    "name": "ai_modeling_project_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
operator_idNo

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 declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds almost nothing beyond that: it does not say what fields the inspection surfaces, whether operator scoping changes the response shape, or what happens if the operator is omitted.

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?

It is a single short sentence with no filler, which is good, but here brevity tips into under-specification rather than economy. The key information (what inspection yields, what the operator scope does) is absent rather than compressed.

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 zero schema description coverage, no output schema, and two parameters, the description carries the full explanatory burden and does not meet it. An agent can guess at project_id but cannot confidently construct operator_id or predict the result.

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 both parameters rest entirely on the description, which only loosely gestures at them via "project" and "selected operator." It never explains what an operator identifier is, its accepted format, or the semantic difference between supplying and omitting operator_id.

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?

"Inspect a Studio project" gives a verb plus resource, and the mention of a "selected operator" hints at scope. But "inspect" is vague about what is actually returned, and nothing distinguishes this from siblings like ai_modeling_canvas_get_project or ai_modeling_project_metadata, which an agent could plausibly choose instead.

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 guidance, no statement of when to prefer this over the many other project-level getters, and no prerequisites. The word "optionally" is the only usage signal, and it applies to a parameter rather than to tool selection.

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