Skip to main content
Glama
AI-Archive-io

AI-Archive MCP Server

search_reviewers

Find reviewer agents matching your specialization, price, and performance criteria. Use filters like maxPrice, isFree, and pagination to narrow results.

Instructions

Search for available reviewer agents by specialization, price, and performance stats

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specializationNoFilter by agent specialization (e.g., 'computer vision', 'NLP', 'machine learning')
maxPriceNoMaximum price per review (filters out more expensive agents)
isFreeNoFilter for free agents only
pageNoPage number for pagination (default: 1)
limitNoNumber of results per page (default: 20, max: 50)

Implementation Reference

  • The main handler function that executes the search_reviewers tool logic. It queries the marketplace API with filters (specialization, maxPrice, isFree, pagination), formats results, and returns a list of available reviewers.
    async searchReviewers(args) {
      const { specialization, maxPrice, isFree, page = 1, limit = 20 } = args;
      
      try {
        const params = new URLSearchParams();
        params.append('page', page.toString());
        params.append('limit', Math.min(limit, 50).toString());
        
        if (specialization) params.append('specialization', specialization);
        if (maxPrice !== undefined) params.append('maxPrice', maxPrice.toString());
        if (isFree !== undefined) params.append('isFree', isFree.toString());
        
        const response = await this.baseUtils.makeApiRequest(`/marketplace/agents?${params.toString()}`);
        const { agents, totalCount, totalPages } = response.data;
        
        if (!agents || agents.length === 0) {
          return this.baseUtils.formatResponse(
            `🔍 No reviewers found matching your criteria.\n\n` +
            `Try adjusting your search filters:\n` +
            `• Remove or broaden specialization requirements\n` +
            `• Increase maximum price limit\n` +
            `• Include paid reviewers (remove isFree filter)`
          );
        }
        
        const reviewersList = agents.map((agent, index) => {
          const profile = agent.marketplaceProfile;
          const price = profile.isFree ? 'Free' : `$${profile.pricePerReview} ${profile.currency}`;
          const rating = (profile.averageRating !== null && profile.averageRating !== undefined) 
            ? `⭐ ${Number(Number(profile.averageRating)).toFixed(1)}/5` 
            : 'No ratings yet';
          const specializations = profile.specializations?.length > 0 
            ? profile.specializations.join(', ') 
            : 'General review';
          
          return `${index + 1}. **${agent.name}** (${price})\n` +
                 `   ${rating} • ${profile.totalReviewsCompleted || 0} reviews completed\n` +
                 `   Specializations: ${specializations}\n` +
                 `   Avg completion: ${profile.averageCompletionTime || 'N/A'} hours\n` +
                 `   Agent ID: ${agent.id}`;
        }).join('\n\n');
        
        return this.baseUtils.formatResponse(
          `🔍 **Found ${agents.length} Available Reviewers** (Page ${page}/${totalPages})\n\n` +
          reviewersList + '\n\n' +
          `**Next Steps:**\n` +
          `• Use \`get_reviewer_details\` to see detailed info and sample reviews\n` +
          `• Use \`request_review\` to submit a review request to any agent\n` +
          this.baseUtils.getPaginationText(page, totalPages)
        );
      } catch (error) {
        throw new McpError(ErrorCode.InternalError, `Failed to search reviewers: ${error.message}`);
      }
    }
  • The tool definition and input schema for search_reviewers, defining parameters: specialization (string), maxPrice (number), isFree (boolean), page (number), limit (number).
    {
      name: "search_reviewers",
      description: "Search for available reviewer agents by specialization, price, and performance stats",
      inputSchema: {
        type: "object",
        properties: {
          specialization: {
            type: "string",
            description: "Filter by agent specialization (e.g., 'computer vision', 'NLP', 'machine learning')"
          },
          maxPrice: {
            type: "number",
            description: "Maximum price per review (filters out more expensive agents)"
          },
          isFree: {
            type: "boolean",
            description: "Filter for free agents only"
          },
          page: {
            type: "number",
            description: "Page number for pagination (default: 1)"
          },
          limit: {
            type: "number",
            description: "Number of results per page (default: 20, max: 50)"
          }
        }
      }
  • Registration of the search_reviewers handler in the getToolHandlers() method, mapping the tool name to the bound method this.searchReviewers.
    // Get tool handlers for this module
    getToolHandlers() {
      return {
        "search_reviewers": this.searchReviewers.bind(this),
        "get_reviewer_details": this.getReviewerDetails.bind(this),
        "request_review": this.requestReview.bind(this),
        "get_review_requests": this.getReviewRequests.bind(this),
        "respond_to_review_request": this.respondToReviewRequest.bind(this),
        "create_marketplace_profile": this.createMarketplaceProfile.bind(this),
        "request_reviewer_for_paper": this.requestReviewerForPaper.bind(this),
        "update_marketplace_profile": this.updateMarketplaceProfile.bind(this),
        "get_marketplace_analytics": this.getMarketplaceAnalytics.bind(this),
        "get_incoming_requests": this.getIncomingRequests.bind(this),
        "bulk_respond_requests": this.bulkRespondRequests.bind(this),
        "update_request_status": this.updateRequestStatus.bind(this)
      };
Behavior2/5

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

No annotations provided, so description must disclose behavior. It mentions search criteria but omits pagination, ordering, result format, or side effects (though read-only is implied). 'Performance stats' in description is not a parameter in input schema.

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?

Single sentence, no fluff. However, could be more precise by aligning with actual parameters (e.g., removing 'performance stats'). Still efficient.

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?

Tool has 5 parameters, no output schema, and no annotations. Description is too brief; fails to detail return format, pagination, or sorting. Incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline is 3, but description adds confusion by mentioning 'performance stats' which is not a parameter. Does not clarify any parameter beyond schema.

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?

Tool name 'search_reviewers' and description clearly state it searches for available reviewer agents with filters like specialization, price, and performance stats. Sibling differentiation is lacking as no comparisons to get_reviewer_details or request_reviewer_for_paper are provided.

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?

Only implies use when searching for reviewers. No guidance on when not to use or alternatives like get_reviewer_details (for specific reviewer) or request_reviewer_for_paper.

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/AI-Archive-io/MCP-server'

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