Skip to main content
Glama

list_menus

Retrieves the complete menu structure from a Norton Guide database file, providing each menu's title, prompt strings, and corresponding guide offsets.

Instructions

Return the menu structure of a Norton Guide database file.

Each menu in the guide is returned as a dictionary describing its title, the list of prompt strings, and the guide offsets associated with each prompt.

Args: path: Absolute path to the .ng file.

Returns: A list of menu dictionaries. Each dictionary contains:

- ``title`` (str): The menu title.
- ``prompts`` (list[str]): The menu prompt strings.
- ``offsets`` (list[int]): The guide offset for each prompt.

Raises: FileNotFoundError: If path does not point to an existing file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions returning data and raises FileNotFoundError, which implies a read operation, but does not explicitly state it is read-only or disclose other behaviors like caching or resource usage.

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 well-structured with a summary, detailed return format, parameter doc, and exception list. Every sentence adds value, and it is appropriately sized for the tool's complexity.

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?

Given the existence of an output schema, the description explains the return format thoroughly. It covers the parameter, return structure, and exceptions. Missing potential examples or notes about performance, but sufficient for a simple tool.

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?

The description compensates for the 0% schema coverage by providing a clear description of the 'path' parameter as 'Absolute path to the .ng file', adding meaning beyond the schema type. It is specific and helpful.

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 tool returns the menu structure of a Norton Guide database file, using specific verbs and a specific resource. It is distinct from sibling tools which focus on searching, navigation, or reading entries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide guidance on when to use this tool over alternatives like list_entries or get_guide_info. No context on when not to use it or prerequisites.

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/davep/ngmcp'

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