Skip to main content
Glama
Nettention

ProudNet Document MCP

Official
by Nettention

search_proudnet_docs

Search ProudNet networking library documentation to find specific topics and technical information for development needs.

Instructions

Search ProudNet documentation for specific topics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for ProudNet documentation

Implementation Reference

  • The function that executes the tool logic for 'search_proudnet_docs'. It scrapes three ProudNet documentation websites using axios and cheerio, searches for the query in link and heading texts, constructs full URLs, collects matching results, and returns a formatted text response with the findings.
    async searchDocs(query) {
      try {
        const urls = [
          'https://docs.proudnet.com/proudnet',
          'https://guide.nettention.com',
          'https://help.nettention.com'
        ];
        
        const results = [];
        
        for (const url of urls) {
          try {
            const response = await axios.get(url);
            const $ = cheerio.load(response.data);
            
            // Search through all links and headings
            $('a, h1, h2, h3, h4').each((_, elem) => {
              const text = $(elem).text().toLowerCase();
              const href = $(elem).attr('href') || $(elem).find('a').attr('href');
              
              if (text.includes(query.toLowerCase())) {
                let fullUrl = null;
                if (href) {
                  if (href.startsWith('http')) {
                    fullUrl = href;
                  } else if (href.startsWith('/')) {
                    const baseUrl = new URL(url);
                    fullUrl = `${baseUrl.origin}${href}`;
                  } else {
                    fullUrl = `${url}/${href}`;
                  }
                }
                
                results.push({
                  title: $(elem).text().trim(),
                  url: fullUrl,
                  source: url,
                  type: elem.name,
                });
              }
            });
          } catch (siteError) {
            console.error(`Failed to search ${url}: ${siteError.message}`);
          }
        }
    
        return {
          content: [
            {
              type: 'text',
              text: results.length > 0 
                ? `Found ${results.length} results for "${query}":\n\n${results.map(r => 
                    `- ${r.title}${r.url ? ` (${r.url})` : ''} [from ${r.source}]`
                  ).join('\n')}`
                : `No results found for "${query}"`,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to search docs: ${error.message}`);
      }
    }
  • Input schema definition for the 'search_proudnet_docs' tool, specifying an object with a required 'query' string property.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search query for ProudNet documentation',
        },
      },
      required: ['query'],
    },
  • server.js:30-43 (registration)
    Registration of the 'search_proudnet_docs' tool in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'search_proudnet_docs',
      description: 'Search ProudNet documentation for specific topics',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query for ProudNet documentation',
          },
        },
        required: ['query'],
      },
    },
  • server.js:74-86 (registration)
    Handler dispatch switch statement in CallToolRequestSchema that routes 'search_proudnet_docs' calls to the searchDocs method.
    switch (name) {
      case 'search_proudnet_docs':
        return await this.searchDocs(args.query);
      
      case 'get_proudnet_page':
        return await this.getPage(args.path);
      
      case 'list_proudnet_sections':
        return await this.listSections();
      
      default:
        throw new Error(`Unknown tool: ${name}`);
    }
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 only states the action ('Search') without details on permissions, rate limits, search scope (e.g., full-text, titles only), result format, or pagination. This is inadequate 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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, 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 the search returns (e.g., list of pages, snippets), how results are ordered, or any limitations. For a search tool with no structured behavioral data, more context is needed.

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 'query' parameter documented as 'Search query for ProudNet documentation'. The description adds no additional meaning beyond this, such as query syntax or examples. Baseline 3 is appropriate 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.

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Search') and resource ('ProudNet documentation'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'get_proudnet_page' or 'list_proudnet_sections', which likely retrieve specific pages or list sections rather than searching content.

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 alternatives. It doesn't mention sibling tools, prerequisites, or specific contexts for searching versus retrieving pages or listing sections, leaving the agent to infer usage from tool names alone.

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