Skip to main content
Glama

Nebula - AI-first B2B digital marketing, Mumbai

List Nebula knowledge items

nebula_list
Read-onlyIdempotent

Read-only browse/enumerate of approved Nebula KB items (title, url, section, date when present). Use to page through a section or the full allowlist; use nebula_search for ranked queries, nebula_section for full record content, nebula_overview for a summary. Returns items[{title,url,section,date?}], total, offset, limit, nextOffset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nebula_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (default 25, max 100)
offsetNoNumber of items to skip (default 0)
sectionNoOptional section id to list (one of: organization, people, services, industries, frameworks, research, externalAssets, pages, answers, blogs). Omit to list all approved sections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / section / description
      Previous value: -"Optional section id to list (one of: organization, people, services, industries, frameworks, research, externalAssets, answers, blogs). Omit to list all approved sections."New value: +"Optional section id to list (one of: organization, people, services, industries, frameworks, research, externalAssets, pages, answers, blogs). Omit to list all approved sections."
    • changedInput schema / properties / section / enum
      Previous value: -[
      -  "organization",
      -  "people",
      -  "services",
      -  "industries",
      -  "frameworks",
      -  "research",
      -  "externalAssets",
      -  "answers",
      -  "blogs"
      -]New value: +[
      +  "organization",
      +  "people",
      +  "services",
      +  "industries",
      +  "frameworks",
      +  "research",
      +  "externalAssets",
      +  "pages",
      +  "answers",
      +  "blogs"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds value by disclosing that only approved items are enumerated and by specifying the returned pagination fields (total, offset, limit, nextOffset), though it does not say what happens at the end of the allowlist or any rate limits.

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?

Two sentences, both earning their place: the first establishes scope and return shape, the second routes to alternatives and documents pagination. The routing guidance is front-loaded rather than buried.

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?

No output schema exists, but the description supplies the full return shape (items with title, url, section, optional date, plus total/offset/limit/nextOffset), which is exactly what an agent needs to consume results. Three simple optional parameters require no further explanation.

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 description coverage is 100%, so limit bounds, offset semantics, and the section enum are fully documented in the schema; baseline is 3. The description's contribution is limited to framing the parameters as pagination and echoing nextOffset, which is helpful but largely redundant.

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 (browse/enumerate) and resource (approved Nebula KB items) plus the fields returned, and immediately separates itself from nebula_search, nebula_section, and nebula_overview. An agent can identify the tool without opening the 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 says when to use it (paging through a section or the full allowlist) and names each sibling with the condition that selects it (ranked queries, full record content, summary). Nothing is left to inference.

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.