Skip to main content
Glama
Nettention

ProudNet Document MCP

Official
by Nettention

get_proudnet_page

Retrieve content from ProudNet documentation pages to access specific guides, API references, and technical information for the networking library.

Instructions

Get content from a specific ProudNet documentation page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the documentation page (e.g., /guides/getting-started)

Implementation Reference

  • The main handler function that fetches the ProudNet documentation page using axios and cheerio, extracts main content and code blocks, and returns formatted text content.
    async getPage(path) {
      try {
        let url;
        
        if (path.startsWith('http')) {
          url = path;
        } else {
          // Default to docs.proudnet.com if no domain is specified
          if (path.includes('guide.nettention.com') || path.includes('help.nettention.com')) {
            url = path.startsWith('/') ? `https:/${path}` : `https://${path}`;
          } else {
            url = `https://docs.proudnet.com${path.startsWith('/') ? path : '/' + path}`;
          }
        }
        
        const response = await axios.get(url);
        const $ = cheerio.load(response.data);
        
        // Remove script and style elements
        $('script, style').remove();
        
        // Extract main content
        const content = $('.content, main, article, [role="main"]').first();
        const text = content.length > 0 
          ? content.text().trim() 
          : $('body').text().trim();
        
        // Extract code examples
        const codeBlocks = [];
        $('pre code, .highlight').each((_, elem) => {
          codeBlocks.push($(elem).text().trim());
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Content from ${url}:\n\n${text.substring(0, 3000)}${text.length > 3000 ? '...' : ''}${
                codeBlocks.length > 0 
                  ? '\n\nCode Examples:\n' + codeBlocks.slice(0, 3).join('\n---\n')
                  : ''
              }`,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to get page: ${error.message}`);
      }
    }
  • Input schema definition for the get_proudnet_page tool, specifying the 'path' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        path: {
          type: 'string',
          description: 'Path to the documentation page (e.g., /guides/getting-started)',
        },
      },
      required: ['path'],
    },
  • server.js:44-57 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
    {
      name: 'get_proudnet_page',
      description: 'Get content from a specific ProudNet documentation page',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path to the documentation page (e.g., /guides/getting-started)',
          },
        },
        required: ['path'],
      },
    },
  • server.js:78-79 (registration)
    Switch case in CallToolRequestHandler that dispatches to the getPage handler method.
    case 'get_proudnet_page':
      return await this.getPage(args.path);
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 'Get[s] content,' implying a read-only operation, but doesn't disclose any behavioral traits like authentication needs, rate limits, error handling, or what 'content' entails (e.g., HTML, markdown). This leaves significant gaps for an AI agent to understand how to use it effectively.

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 with zero wasted words. It's appropriately sized for a simple tool and front-loaded with the core purpose, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'content' is returned (e.g., format, structure) or address potential behavioral aspects like errors or limitations. For a tool with no structured data beyond the input schema, this leaves the AI agent with insufficient context to use it reliably.

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?

The input schema has 100% description coverage, with the 'path' parameter well-documented in the schema itself. The description adds no additional meaning beyond implying the parameter is for a 'specific' page, which is already clear from the schema. This meets the baseline score of 3 when schema coverage is high.

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 verb ('Get') and resource ('content from a specific ProudNet documentation page'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_proudnet_sections' or 'search_proudnet_docs' beyond implying it retrieves a single page rather than listing or searching.

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 provides no guidance on when to use this tool versus its siblings. It mentions retrieving a 'specific' page, which hints at usage when the exact path is known, but doesn't explicitly state alternatives or exclusions, such as using 'search_proudnet_docs' for unknown paths or 'list_proudnet_sections' for browsing.

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