Skip to main content
Glama
Guitarmaniac24

GetABrain🧠 | Live Human-in-the-Loop MCP for AI Agents

list_queries

Read-only

Retrieve a summary of your recent GetABrain queries, sorted by newest first. Filter by status to find active or pending queries or recover a lost query ID.

Instructions

List your recent GetABrain queries, most recent first. Use this to get an overview of past/active queries, recover a query_id you lost track of, or filter by status (e.g. find everything still "active" or "pending"). Read-only, no cost. Disambiguation: this lists MANY queries at a summary level; it does not return the individual worker responses for any one query -- use get_responses or wait_for_responses with a specific query_id for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of queries to return, most recent first (1-100, default server-side).
statusNoOptional filter to only return queries in this status (e.g. "active", "pending", "completed", "cancelled", "failed", "expired"). Omit to return all statuses.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
totalNo
offsetNo
queriesNo
has_moreNo
Behavior4/5

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

Beyond annotations (readOnlyHint, openWorldHint), description adds ordering ('most recent first'), cost ('no cost'), and summary-level scope. It also mentions status filtering capability.

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

Conciseness4/5

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

Description is well-structured: purpose, usage, then disambiguation. It is fairly concise, though slightly verbose with multiple sentences. Front-loaded with main action.

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?

Given the presence of an output schema and low complexity (2 optional params), the description covers purpose, usage, and disambiguation adequately. No significant gaps.

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 coverage is 100% with good descriptions for both parameters. The description reinforces filtering use case but does not add meaning beyond schema (e.g., formats, defaults). Baseline 3 is appropriate.

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 clearly states it lists recent queries in reverse chronological order, using a specific verb ('List') and resource ('GetABrain queries'). It also distinguishes itself from siblings by noting it does not return individual responses.

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?

Provides explicit use cases: getting an overview, recovering a query_id, filtering by status. Also gives clear when-not-to-use guidance: for individual responses, use get_responses or wait_for_responses.

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/Guitarmaniac24/getabrain-mcp-server'

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