forge3d-mcp

List Providers

list_providers

Check which text-to-3D providers are configured and verified before selecting a hosted backend; set check=true to confirm credentials with a live authenticated request.

Instructions

List text-to-3D providers: what is configured here, and what is verified.

Call this before choosing backend="hosted". available means credentials exist on this machine; verified means the adapter has been exercised against a live account by the maintainer. Most commercial adapters are NOT verified — pass check=true to make a real authenticated request and settle it.

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": "list_providers"
  }
}

Input Schema

Name	Required	Description	Default
`check`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.7Nov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one important cost: `check=true` performs a real authenticated request, and most commercial adapters are unverified by default. It does not say whether the tool itself is read-only, what credentials or permissions are needed, or how slow/expensive the default path is.

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?

Front-loaded with the action and scope, then the call-order rule, then field semantics. Four short lines, each adding information; only the "settle it" phrasing is slightly informal rather than precise.

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-shape explanation is not required, yet the description usefully defines the two flags that drive a decision. For a one-parameter list tool, the remaining gap (no statement of permissions, latency, or the `list_backends` relationship) is minor.

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 0%, so the description must compensate for the single `check` boolean — and it partly does, explaining that `check=true` triggers a live authenticated request and settles the verified state. It never states the default is false or what the returned `available`/`verified` flags mean structurally, which matters more given the bare schema.

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 first sentence states a specific verb and resource ("List text-to-3D providers") and narrows scope to two attributes: what is configured and what is verified. That is clearly distinct from a generic backend listing, though it never names the sibling `list_backends` to make the split explicit.

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?

Gives an explicit precondition: "Call this before choosing `backend=\"hosted\"`", which tells the agent exactly where this tool sits in a workflow. It also gives guidance on when to escalate to `check=true`. It stops short of naming alternatives or stating when this tool should not be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.