Skip to main content
Glama

List what can be built in R3

r3_factory_list
Read-onlyIdempotent

List the R3 factories available to r3_factory_run, with each one's options, types and defaults. A factory builds a complete, correctly-wired object — a cube is a mesh plus geometry plus material plus colour, already connected. Call this before r3_factory_run if you are unsure of a factory name or its options.

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

Input Schema

NameRequiredDescriptionDefault
factoryNoOptional: return only this factory, e.g. "Cube". Omit for all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: here the return payload is a catalogue of factory names with their options, types and defaults, and it clarifies that the tool is a discovery step rather than an action. It stops short of describing output shape or ordering, which is a minor gap for a list tool.

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?

Three short sentences: what it does, a concrete clarifying example, and a usage rule. Front-loaded with the action and free of filler.

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

Completeness5/5

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

A single optional filter parameter, no output schema and no nested objects — an agent needs only to know what the catalogue contains and when to call it, both of which the description supplies. Nothing material is missing for correct invocation.

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 single optional `factory` parameter is already documented with an example, so the schema does the heavy lifting. The description mentions listing options/types/defaults but adds no syntax or filtering detail beyond what the schema states. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("List the R3 factories available to r3_factory_run") and immediately names what is returned (options, types, defaults). It goes further by explaining what a factory produces ("a cube is a mesh plus geometry plus material plus colour, already connected"), which makes the resource concept unambiguous against siblings like r3_factory_run.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states an explicit routing rule: call this before r3_factory_run when unsure of a factory name or its options. The alternative tool is named and the condition that selects it is spelled out, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources