Skip to main content
Glama

list_asset_providers

Lists configured asset providers and reports credential status without exposing secrets, helping verify available 3D asset sources and authentication state.

Instructions

List configured asset providers and credential status (no secrets).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 burden, and it does disclose one genuinely useful behavioral fact: credential status is surfaced but secrets are never returned, which reassures the agent that the output is safe to echo. It does not say whether providers are probed live (network/permission cost), what a failed or expired credential looks like, or how unconfigured providers appear, so meaningful behavioral gaps remain.

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

Conciseness5/5

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

A single sentence, front-loaded with the verb and resource, with the qualifying parenthetical attached exactly where it matters. Nothing is padding and nothing is buried.

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?

Tool complexity is minimal (no parameters) and an output schema exists, so the description need not enumerate return fields. Given that, the sentence covers the resource and the key safety caveat; only live-probe behavior and error states are unaddressed, which are secondary.

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 no parameters, so there is nothing for the description to disambiguate and the baseline applies. The parenthetical '(no secrets)' clarifies what will appear in output rather than input, which is a small but relevant addition.

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 and resource ('List configured asset providers') and adds a second dimension of value ('credential status'), so the agent knows this is not just an enumeration but also a status report. It does not explicitly contrast itself with lookalike listing siblings such as list_materials, but the resource is distinct enough to be unambiguous.

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: the phrase 'configured asset providers' hints that this is the discovery step before asset operations like import_asset or export_asset, but the description never says when to call it, in what order, or what to do if nothing is configured. For a zero-parameter read tool this is acceptable but leaves the agent to infer placement in a workflow.

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