tools/list — every public Particle tool is executable by name, so prefer calling discovered tools directly when your harness allows it. It’s always-on (the system category can never be excluded) and free to invoke (tier free, cost 0).
Identical metering and plan gating apply whether you call a tool directly or through particle_call — the dispatch path mirrors a direct call exactly (request log, metering, pricing gate, premium gate, execute), and the inner tool’s output_format is honored. Use particle_catalog to discover tool names and input schemas.
Inputs
Unknown or internal tool names return an actionable error suggesting
particle_catalog. The MCP surface’s contract is that “all tools” means all public tools — internal tools are never dispatchable here even though the registry could run them.
Output
The target tool’s own response, passed through unchanged — the same markdown text block the tool would return if called directly (or its JSON form when the innerarguments include output_format: "json"). A call through particle_call is indistinguishable from a direct one.
Example
Related
- Tool sets & discovery — why every public tool is callable by name regardless of advertisement.
particle_catalog— discover tool names and input schemas first.