Skip to main content
Glama

brainkb_qa_list

Find a canned question BrainKB can answer, then run it with brainkb_qa_run.

Prefer these over writing SPARQL: they are vetted against BrainKB's actual
vocabulary. Discovery is two steps, so you never read every query at once:

1. brainkb_qa_list() -> the menu: each category's name, a description of
   the questions it covers, and how many queries it has. Pick the category
   whose description matches the user's question.
2. brainkb_qa_list(category="<name>") -> that category's queries. Each has
   `question` (what it answers), `notes` (when to use it, where parameter
   values come from, what the results mean), `params` (required ones have
   no default — ask the user rather than guess) and a working `example`.

`search="words"` filters queries by words in their id/question/notes; use it
alone to search every category when none of the descriptions fits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it discloses the two-phase discovery model, the shape of returned items (`question`, `notes`, `params`, `example`), and the behavioral rule that required params 'have no default — ask the user rather than guess.' It does not mention permissions or scale limits, but for a discovery/list tool that is a minor omission.

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?

Front-loaded with the core action and the paired run tool before the numbered discovery steps, and every sentence carries information. It is somewhat long at roughly ten lines, but the structure is scannable and no line is 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?

For a two-parameter discovery tool with no annotations and no output schema, the description covers purpose, workflow, the returned field structure, and both parameters' semantics. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 0%, so the description must compensate, and it largely does: `search` is defined as filtering by words in id/question/notes (and its alone-use semantic is stated), and `category` is shown to select a category segment. It leaves unstated what happens when both are supplied and treats defaults (empty string) only implicitly.

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?

States a specific verb and resource ('Find a canned question BrainKB can answer') and immediately names the paired sibling brainkb_qa_run. An agent can distinguish it from brainkb_qa_run, brainkb_sparql, and brainkb_search without inspecting any schema.

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?

Explicitly states when to prefer this over writing SPARQL ('vetted against BrainKB's actual vocabulary'), lays out the exact two-step call sequence, and specifies the lone-use condition for `search` ('when none of the descriptions fits'). When-to-use and alternative routing are fully covered.

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.