Skip to main content
Glama

research_and_ask

Research any topic and get cited answers to your questions in a single call. Creates a notebook, imports top sources, runs Q&A, and cleans up by default.

Instructions

One-shot: create ephemeral notebook → research → import sources → Q&A.

Full workflow wrapped in a single call:

  1. Create a fresh empty notebook.

  2. research_start(topic) → candidate URLs.

  3. Import the top max_sources URLs as sources.

  4. For each question in questions, run notebook_query.

  5. If keep_notebook is False (default), delete the notebook.

Returns { notebook_id, # str if kept, None if deleted topic, sources_imported, # [{url, title, word_count}, ...] qa, # [{question, answer, source_count, chunks}, ...] kept, # bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYes
questionsYes
max_sourcesNo
keep_notebookNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does so well: it discloses the ephemeral notebook lifecycle, deletion behavior (default keep_notebook=False), and the return fields including notebook_id=None when deleted. It exposes the primary side effect (notebook deletion) clearly.

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?

The description is efficiently structured: a one-line summary, numbered steps, and a compact return block. Every line adds value, and the format makes the workflow easy to follow without fluff.

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 composite tool with 4 parameters and multiple side effects, the description is highly complete. It covers the full workflow, default behavior, deletion consequences, and the return structure in detail—especially valuable given the lack of annotation support and zero schema descriptions.

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 description coverage is 0%, but the description adds meaning for all four parameters: 'topic' seeds research, 'questions' drives notebook_query, 'max_sources' controls how many URLs are imported, and 'keep_notebook' determines deletion. This compensates well for the schema's lack of descriptions.

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 identifies a composite workflow: create ephemeral notebook, research, import sources, and answer questions. It uses specific verbs and resource names, and the 'One-shot' framing distinguishes it from granular sibling tools like research_start and notebook_query.

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?

The description conveys when to use this tool: as a one-shot wrapper for a multi-step research and Q&A workflow. It does not explicitly state when not to use it or mention alternatives for more granular control, but the intended context is clear.

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/gracelee087/notebooklm-mcp-lisa'

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