Skip to main content
Glama
yvanfreitas

MCP Test Server

by yvanfreitas

get_users

Retrieve user data from the mock database with optional role-based filtering for admin, user, or moderator roles.

Instructions

Get all users from the mock database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoFilter users by role (admin, user, moderator)

Implementation Reference

  • The static method getAll in UserService that executes the get_users tool logic: filters users by optional role and returns them.
    static getAll(filters = {}) {
      let filteredUsers = users;
      
      if (filters.role) {
        filteredUsers = filteredUsers.filter(user => user.role === filters.role);
      }
    
      return {
        success: true,
        data: filteredUsers,
        total: filteredUsers.length
      };
    }
  • Input/output schema definition for the get_users tool.
    {
      name: 'get_users',
      description: 'Get all users from the mock database',
      inputSchema: {
        type: 'object',
        properties: {
          role: {
            type: 'string',
            description: 'Filter users by role (admin, user, moderator)',
            enum: ['admin', 'user', 'moderator']
          }
        }
      }
    },
  • mcp-server.js:38-46 (registration)
    Registration of available tools list, including the get_users schema via userToolSchemas.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          ...userToolSchemas,
          ...taskToolSchemas,
          searchToolSchema
        ]
      };
    });
  • mcp-server.js:54-55 (registration)
    Dispatch/handling registration for the get_users tool call, invoking the handler.
    case 'get_users':
      return createMcpResponse(UserService.getAll(args));
  • Import of mock users data used by the get_users handler.
    import { users } from '../data/mockData.js';
    
    export class UserService {
      static getAll(filters = {}) {
        let filteredUsers = users;
        
        if (filters.role) {
          filteredUsers = filteredUsers.filter(user => user.role === filters.role);
        }
    
        return {
          success: true,
          data: filteredUsers,
          total: filteredUsers.length
        };
      }
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 it retrieves data ('Get'), implying a read-only operation, but doesn't mention potential behaviors like pagination, rate limits, authentication requirements, or what happens if the database is empty. This leaves significant gaps for a tool that interacts with a database.

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, direct sentence with no wasted words. It front-loads the core action and resource, making it efficient and easy to parse. Every part of the sentence contributes essential information.

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 for a database query tool. It doesn't explain the return format (e.g., list of user objects), error conditions, or any limitations (like maximum result size). For a tool with one parameter and no structured behavioral hints, more context is needed to guide effective use.

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 'role' parameter fully documented including its enum values. The description doesn't add any parameter-specific information beyond implying retrieval of 'all users', which aligns with the optional filtering via 'role'. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 ('Get') and resource ('all users from the mock database'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_user' (singular) or 'search', which might also retrieve user data, so it doesn't reach the highest score.

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 like 'get_user' (for a single user) or 'search' (which might offer more flexible filtering). It mentions retrieving 'all users' but doesn't clarify if this is the preferred method for bulk retrieval or if there are performance considerations.

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/yvanfreitas/MCP-test'

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