Skip to main content
Glama

get_ideas

Retrieve your captured ideas from a chosen time window, newest first, to revisit and act on them.

Instructions

List captured ideas from your knowledge base, newest first.

Use this to review what you've been thinking about over a chosen time
window — the ideas you logged with capture_idea — so you can revisit,
connect, or act on them. Pairs with capture_idea (to add) and
cross_pollinate (to surface related work).

Args:
    scope: Time window to retrieve. One of "today", "week" (last 7 days),
        "month" (last 30 days), or "all". Defaults to "week".
    limit: Maximum number of ideas to return, newest first. Defaults to 20.

Returns:
    A formatted list of matching ideas with their timestamps and tags, or a
    friendly note if none were found in that window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoweek
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so description bears full burden. It describes read-only behavior, output format (list with timestamps/tags), and default sorting. Could mention pagination or absence of side effects explicitly, but current level is sufficient.

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?

Concise: first sentence captures core function, followed by usage context, sibling references, and clear Args/Returns sections. No redundant words.

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 low complexity (2 params, no required, output schema exists), the description covers operation, usage context, parameter details, and return format completely. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description fully explains both parameters: scope with enumerated options and defaults ('today', 'week', 'month', 'all'), limit as max count, and ordering context. This adds significant meaning beyond the 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?

The description clearly states the verb 'List captured ideas' and resource 'knowledge base', with explicit ordering ('newest first'). It distinguishes from siblings by naming complementary tools (capture_idea, cross_pollinate).

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 when-to-use: 'review what you've been thinking about over a chosen time window' and identifies alternatives ('Pairs with capture_idea... cross_pollinate').

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/SVerITG/Metis_PH'

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