Skip to main content
Glama

ask-all

Read-only

Send one question to GPT, Gemini, Grok, and OpenRouter models in parallel to collect independent second opinions.

Instructions

Fan out one question to GPT, Gemini, Grok, and any configured OpenRouter models in parallel for independent second opinions, then return all results (advisory, no cross-contamination). Pass expert to apply a persona to every delegate. Calls external LLM providers (each needs its key/CLI; provider rate limits apply); returns a text-wrapped JSON envelope { results[], omitted[] } and persists a session record only when sessions.persist is enabled (default off).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory the provider runs in (used to resolve relative file refs). Defaults to the server process directory.
filesNoOptional attachments for providers that read files (Grok/OpenRouter; inlined as context for Codex/Gemini). Each item is EXACTLY ONE of path/dir/file_id/file_url.
expertNoOptional persona: architect, plan-reviewer, scope-analyst, code-reviewer, security-analyst, researcher, or debugger. On a named expert tool the tool's own persona wins and this is ignored.
promptYesThe question or task for the provider(s)/expert.
reasoningEffortNoReasoning depth where the provider supports it (Grok, OpenRouter): low, medium, high, or none. CLI providers (Codex, Gemini) ignore it.
developerInstructionsNoOptional system/developer instructions injected verbatim; overrides the built-in persona for `expert`.
Behavior5/5

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

Discloses external provider calls, key/CLI requirements, rate limits, return format (JSON envelope with results/omitted), and session persistence condition. Adds significant value beyond readOnlyHint annotation.

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?

Two well-structured sentences front-load the core action and include all key caveats without superfluous content.

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?

Given 6 parameters, no output schema, and complex multi-provider behavior, the description adequately covers purpose, behavior, output format, and configuration details.

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?

Schema covers all 6 params (100% coverage). Description adds context: expert applies persona, reasoningEffort ignored by some providers, cwd resolution, and default persistence behavior. Enhances understanding beyond schema.

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?

Clearly states the tool fans out a question to multiple LLM providers (GPT, Gemini, Grok, OpenRouter) in parallel for independent second opinions, distinguishing it from single-provider siblings.

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?

Indicates use for independent second opinions and advisory results. Implicitly contrasts with single-provider tools via sibling names, but lacks explicit when-not or alternative references.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/antonbabenko/deliberation'

If you have feedback or need assistance with the MCP directory API, please join our Discord server