> ## Documentation Index
> Fetch the complete documentation index at: https://docs.particle.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# particle_call

> Dispatch any public Particle tool by name — a compatibility fallback for harnesses that block un-advertised tools.

Dispatch any public Particle tool by name. This is a **compatibility fallback** for harnesses that block calling tools that weren't advertised on `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`](/mcp/tools/system/catalog) to discover tool names and input schemas.

## Inputs

| Field       | Type   | Required | Default | Description                                                                                                                        |
| ----------- | ------ | -------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `tool`      | string | yes      | —       | Flat name of any public Particle tool (e.g. `"particle_podcast_get_episode"`). Discover names and schemas with `particle_catalog`. |
| `arguments` | object | no       | `{}`    | Arguments object for the target tool, matching its input schema.                                                                   |

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 inner `arguments` include `output_format: "json"`). A call through `particle_call` is indistinguishable from a direct one.

## Example

```text theme={"dark"}
# Harness blocks un-advertised tool_use names; reach an opt-in tool via the fallback.
Agent calls: particle_call {
  "tool": "particle_podcast_get_bias_leaderboard",
  "arguments": { "metric": "most_right_leaning", "limit": 10 }
}
            → returns the same output as calling particle_podcast_get_bias_leaderboard directly
```

## Related

* [Tool sets & discovery](/mcp/tool-sets) — why every public tool is callable by name regardless of advertisement.
* [`particle_catalog`](/mcp/tools/system/catalog) — discover tool names and input schemas first.