Skip to main content
Glama
davep

ngmcp

by davep
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_guide_info

Retrieve metadata from a Norton Guide database file, including title, credits, and file validation status.

Instructions

Return metadata for a Norton Guide database file.

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

Returns: A dictionary with the following keys:

- ``path`` (str): Resolved path to the guide.
- ``title`` (str): Guide title.
- ``credits`` (list[str]): Up to five credit lines.
- ``magic`` (str): Two-character magic marker (``"NG"`` or ``"EH"``).
- ``made_with`` (str): Tool used to build the guide.
- ``menu_count`` (int): Number of menus in the guide.
- ``file_size`` (int): File size in bytes.
- ``is_valid`` (bool): Whether the file is a recognised Norton Guide.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Details return dictionary structure including keys, types, and FileNotFoundError. No annotations provided, so description carries full burden; could explicitly state read-only nature but implication is clear.

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?

Structured with Args/Returns/Raises sections, but somewhat verbose with full Python docstring. Information is front-loaded and well-organized, though could be more terse.

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?

Comprehensive: covers single parameter, detailed return values with types, and error handling. No gaps given the tool's simplicity (one param, no nested objects).

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?

Despite 0% schema coverage, description fully explains 'path' as 'Absolute path to the .ng file' and enumerates return dictionary keys, adding significant meaning beyond 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?

Clearly states 'Return metadata for a Norton Guide database file', specifying the resource (.ng file) and action (metadata retrieval). Distinguishes from siblings like list_menus or read_entry.

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

Usage Guidelines4/5

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

Describes when to use: when metadata of a .ng file is needed, with clear parameter requirement. No exclusions or alternatives mentioned, but context with siblings implies differentiation.

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