Skip to main content
Glama
JoseGarayar

MCP Employee API Server

by JoseGarayar

get_employee

Retrieve specific employee records by ID from the MCP Employee API Server. Use this tool to access detailed employee information for management or verification purposes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • main.py:49-53 (handler)
    The main handler function for the 'get_employee' MCP tool. It is decorated with @mcp.tool() to register it, takes an employee ID as input, constructs the API URL, calls the make_request helper to fetch data from the backend API, and returns the response dictionary.
    @mcp.tool()
    async def get_employee(id: int) -> dict:
        url = f"{URL_BASE}/employees/{id}"
        response = await make_request(url)
        return response
  • main.py:13-40 (helper)
    Shared helper utility function used by 'get_employee' and other tools to perform HTTP requests to the employee API backend, handling GET, POST, PUT, DELETE methods with proper headers, timeouts, and error handling.
    async def make_request(url: str, method: str = "GET", json_data: dict = None) -> dict[str, Any] | None:
        """Make a request to the API with proper error handling for all HTTP methods."""
        headers = {
            "User-Agent": USER_AGENT,
            "Accept": "application/json"
        }
        
        # Add Content-Type header for requests with JSON data
        if json_data is not None:
            headers["Content-Type"] = "application/json"
        
        async with httpx.AsyncClient() as client:
            try:
                if method.upper() == "GET":
                    response = await client.get(url, headers=headers, timeout=30.0)
                elif method.upper() == "POST":
                    response = await client.post(url, headers=headers, json=json_data, timeout=30.0)
                elif method.upper() == "PUT":
                    response = await client.put(url, headers=headers, json=json_data, timeout=30.0)
                elif method.upper() == "DELETE":
                    response = await client.delete(url, headers=headers, timeout=30.0)
                else:
                    raise ValueError(f"Unsupported HTTP method: {method}")
                
                response.raise_for_status()
                return response.json()
            except Exception:
                return None
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/JoseGarayar/mcp_test'

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