Skip to main content
Glama
shazaaly

MCP Boilerplate Server

by shazaaly

get_user_info

Retrieve user details by providing a user ID to access specific information from the server's user management system.

Instructions

Get user information by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool that implements the get_user_info tool. It takes a user_id and returns mock user information or an error if not found.
    @mcp.tool
    def get_user_info(user_id: int) -> dict:
        """Get user information by ID"""
        mock_users = {
            1: {"name": "Alice", "email": "alice@example.com", "role": "admin"},
            2: {"name": "Bob", "email": "bob@example.com", "role": "user"},
            3: {"name": "Charlie", "email": "charlie@example.com", "role": "user"}
        }
        return mock_users.get(user_id, {"error": "User not found"})
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a read operation ('Get'), implying non-destructive, but doesn't disclose permissions, rate limits, error handling, or return format. For a tool with no annotations, this leaves significant behavioral gaps.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 low complexity (1 parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and 0% schema coverage, it lacks behavioral and parametric details that would enhance completeness for agent 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?

Schema description coverage is 0%, but the description adds meaning by specifying the parameter is 'by ID'. However, it doesn't detail the ID format, constraints, or examples. With 1 parameter, the baseline is 4, but the minimal addition slightly compensates for the schema gap.

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 ('user information'), specifying it's by ID. It doesn't distinguish from siblings, but none are related tools (add, greet, multiply), so differentiation isn't needed. It's specific enough to understand the core function.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions. With unrelated siblings, explicit alternatives aren't needed, but general usage context is missing.

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/shazaaly/mcp-boilerplate'

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