Skip to main content
Glama
Nettention

ProudNet Document MCP

Official
by Nettention

list_proudnet_sections

Retrieve main sections of ProudNet networking library documentation to navigate and access specific content areas.

Instructions

List main sections of ProudNet documentation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that scrapes navigation links from ProudNet documentation websites (docs.proudnet.com, guide.nettention.com, help.nettention.com) to list main sections, formats them, and returns as MCP content.
    async listSections() {
      try {
        const urls = [
          'https://docs.proudnet.com/proudnet',
          'https://guide.nettention.com',
          'https://help.nettention.com'
        ];
        
        const allSections = [];
        
        for (const url of urls) {
          try {
            const response = await axios.get(url);
            const $ = cheerio.load(response.data);
            
            const sections = [];
            
            // Find navigation or main sections
            $('.nav-link, .sidebar a, nav a, [class*="menu"] a').each((_, elem) => {
              const text = $(elem).text().trim();
              const href = $(elem).attr('href');
              
              if (text && href && !sections.find(s => s.title === text)) {
                let fullPath = href;
                if (!href.startsWith('http')) {
                  if (href.startsWith('/')) {
                    const baseUrl = new URL(url);
                    fullPath = `${baseUrl.origin}${href}`;
                  } else {
                    fullPath = `${url}/${href}`;
                  }
                }
                
                sections.push({
                  title: text,
                  path: fullPath,
                  source: url,
                });
              }
            });
            
            allSections.push({
              site: url,
              sections: sections.slice(0, 10)
            });
          } catch (siteError) {
            console.error(`Failed to get sections from ${url}: ${siteError.message}`);
          }
        }
    
        const formattedSections = allSections.map(site => 
          `From ${site.site}:\n${site.sections.map(s => 
            `- ${s.title}: ${s.path}`
          ).join('\n')}`
        ).join('\n\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `Documentation Sections:\n\n${formattedSections}`,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to list sections: ${error.message}`);
      }
    }
  • server.js:58-65 (registration)
    Tool registration in the ListTools response, including name, description, and input schema (no required parameters).
    {
      name: 'list_proudnet_sections',
      description: 'List main sections of ProudNet documentation',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the tool: an empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • server.js:81-82 (handler)
    Dispatch case in the CallToolRequest handler that invokes the listSections method.
    case 'list_proudnet_sections':
      return await this.listSections();
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists sections but doesn't mention whether it's read-only, safe, or has any side effects, rate limits, or authentication needs. This is a significant gap for a tool with zero annotation coverage.

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 a single, clear sentence that efficiently conveys the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It lacks behavioral context and usage guidelines, making it incomplete for optimal agent understanding, though it suffices for basic functionality.

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 tool has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this case is 4, as the description appropriately avoids redundant information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and resource ('main sections of ProudNet documentation'), providing a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'get_proudnet_page' or 'search_proudnet_docs', which might handle similar content differently.

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 offers no guidance on when to use this tool versus alternatives like 'get_proudnet_page' or 'search_proudnet_docs'. It lacks context on prerequisites, exclusions, or specific scenarios, leaving usage ambiguous.

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/Nettention/proudnet-document-mcp'

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