Skip to main content
Glama

Nebula - AI-first B2B digital marketing, Mumbai

Read a Nebula section

nebula_section
Read-onlyIdempotent

Read-only fetch of one exact section or record by dotted path. Sections: organization, people, services, industries, frameworks, research, externalAssets, pages, answers, blogs. Use when you know the path from search/list; use nebula_overview for a summary, nebula_search to find paths, nebula_list to browse titles. Returns path plus value, or for list sections: items, total, offset, limit, nextOffset. Examples: "services", "answers.4", "organization.address".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "nebula_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDotted path, e.g. "industries" or "answers.0"
limitNoFor list sections: items per page (default 20)
offsetNoFor list sections: first item index (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the description correctly spends its budget elsewhere. It adds genuinely new behavior: the two return shapes (path plus value vs. items/total/offset/limit/nextOffset for list sections), which matters since there is no output schema. It does not mention error behavior on an invalid path or any auth/rate constraints.

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, then sections, then routing, then return shape, then examples — a logical order with no filler sentences. The ten-item section enumeration is long but functional, since it defines the valid path roots.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with full annotation coverage and no output schema, the definition covers purpose, alternatives, return shape, and path examples. Remaining gaps are minor: what an invalid path returns and which sections are paginated lists versus single records are only implied by the return-shape sentence.

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 coverage is 100%, so path, limit, and offset are already documented with defaults and bounds; the description's dotted-path examples overlap the schema's own examples. It does clarify that limit/offset apply only to list sections, which is modest added meaning over the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ("Read-only fetch of one exact section or record by dotted path") and enumerates the addressable sections, so the agent knows precisely what it retrieves. It is clearly distinguishable from nebula_list, nebula_search, and nebula_overview by contrast in the following sentence.

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 the selecting condition ("Use when you know the path from search/list") and routes to each alternative with its own condition: overview for summaries, search to find paths, list to browse titles. No inference required.

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.