Skip to main content
Glama
mordor-forge

trident-mcp

by mordor-forge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

list_models

Read-only

Lists model versions this MCP server knows per tool, with aliases, defaults, and rejected options, so you can pick a compatible version before generation.

Instructions

List the model versions this server knows, per tool, with aliases, defaults and the options each version rejects. Static; unknown versions are still sent to Tripo with a warning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoOnly list model versions this tool accepts, e.g. text_to_model or rig_model

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelsYes
checked_onYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.4.0
    • addedInput schema / properties
      Added value: +{
+  "operation": {
+    "description": "Only list model versions this tool accepts, e.g. text_to_model or rig_model",
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / checked_on
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / models / items / properties / capabilities
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": [
-    "null",
-    "array"
-  ]
-}
    • removedOutput schema / properties / models / items / properties / default
      Removed value: -{
-  "type": "boolean"
-}
    • addedOutput schema / properties / models / items / properties / default_for
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedOutput schema / properties / models / items / properties / family
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / models / items / properties / namespace
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / models / items / properties / operations
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedOutput schema / properties / models / items / properties / rejects
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedOutput schema / properties / models / items / properties / stage
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / models / items / required
      Previous value: -[
-  "name",
-  "id",
-  "description",
-  "capabilities"
-]New value: +[
+  "id",
+  "name",
+  "family",
+  "description",
+  "operations"
+]
    • changedOutput schema / required
      Previous value: -[
-  "models"
-]New value: +[
+  "checked_on",
+  "models"
+]
  2. Changed3 schema fields changedv0.3.0
    • addedOutput schema / properties / models / items / properties / aliases
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedOutput schema / properties / models / items / properties / default
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / models / items / properties / namespace
      Added value: +{
+  "type": "string"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and non-open-world safety, but the description still adds real context: the result is static (no live lookup), it enumerates aliases/defaults/rejected options, and unknown versions are passed through with a warning rather than hard-failing. It does not explain why idempotentHint is false, which is the one unexplained annotation.

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?

One compact sentence, front-loaded with the core action and resource, with the parenthetical detail arriving after. It is dense but every clause carries information; nothing is padded.

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

Completeness4/5

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

An output schema exists, so return-value explanation is not required, and the description still previews what the list contains. Combined with full schema coverage for the single optional parameter, an agent has enough to invoke it correctly; only the idempotency caveat is left dangling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the sole 'operation' parameter is fully documented in the schema. The description's 'per tool' phrasing echoes that meaning without adding format, enum, or default details beyond it, so the baseline of 3 applies.

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?

States a specific verb+resource (list model versions) and scopes it clearly as 'per tool', with the payload contents named (aliases, defaults, rejected options). It reads distinctly from siblings like get_config or get_usage, though it never explicitly contrasts itself with them.

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: an agent can infer it should call this before picking a model version, and the 'static; unknown versions are still sent to Tripo with a warning' line hints at validation semantics. There is no explicit when-to-use versus alternatives and no named alternative tool.

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