Skip to main content
Glama

recent_briefs

Retrieve recent draft and promoted briefs from your workspace. Build list of brief activity without reading full resource URIs.

Instructions

List recent public Nogra briefs.

    Returns recent draft JSON and promoted markdown briefs from the configured workspace brief substrate.

    When to use:
    - Build caller-driven brief lists through tools.
    - Inspect recent draft and promoted brief activity without reading resource URIs.

    When NOT to use:
    - Do not use this to read a specific brief body; use brief_read.
    - Do not use this to create or promote briefs; use the write lifecycle tools.

    Examples:
    >>> recent_briefs(limit=10)
    {"workspaceId": "local", "briefs": [...]}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of recent draft and promoted briefs to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, but description explains return of draft JSON and promoted markdown briefs, and example output. Lacks discussion of permissions or side effects, but covers main behavior.

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?

Well-structured with sections, concise, and includes an example. No 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?

Output schema exists, so return value details are covered. Description provides additional context about workspaceId and briefs in example. Single parameter is well-documented.

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?

Only one parameter (limit) with 100% schema coverage. Description adds context by showing example usage and clarifying that it returns both drafts and promoted briefs.

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?

Specifies verb 'list', resource 'recent public Nogra briefs', and differentiates from siblings like brief_read and write lifecycle tools.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear context and mention alternatives (brief_read, write lifecycle tools).

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/nograai/nogra-mcp'

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