Skip to main content
Glama
yeison-liscano

Simple HTTP MCP Server

Get Time

get_time
Idempotent

Retrieve the current time via JSON-RPC on the Simple HTTP MCP Server. Designed for remote execution, it provides accurate time data for integration into client applications.

Instructions

Get the current time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeYesThe current time

Implementation Reference

  • The handler function for the 'get_time' tool, which returns the current time in HH:MM:SS format using UTC.
    async def get_time() -> GetTimeOutput:
        """Get the current time."""
        return GetTimeOutput(time=datetime.now(UTC).strftime("%H:%M:%S"))
  • Pydantic output schema for the 'get_time' tool, defining the 'time' field.
    class GetTimeOutput(BaseModel):
        time: str = Field(description="The current time")
  • Registration of the 'get_time' tool in the TOOLS tuple, specifying function, no inputs, and output schema.
    Tool(
        func=get_time,
        inputs=type(None),
        output=GetTimeOutput,
    ),
Behavior3/5

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

Annotations already provide key behavioral hints (readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false), so the description doesn't need to repeat these. However, it adds no additional context about rate limits, authentication needs, or specific behavioral traits beyond the basic action, resulting in a baseline score.

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 extremely concise and front-loaded with a single, clear sentence that directly states the tool's purpose. There is no wasted language or unnecessary elaboration.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, annotations covering key behaviors, and an output schema present), the description is complete enough for basic understanding. However, it lacks any usage context or differentiation from siblings, which slightly reduces completeness.

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

Parameters4/5

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

With 0 parameters and 100% schema description coverage, the schema fully documents the lack of inputs. The description implicitly confirms this by not mentioning any parameters, which is appropriate. A baseline of 4 is given as no parameters are present.

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 ('Get') and resource ('current time'), making it immediately understandable. However, it doesn't distinguish itself from potential sibling tools like 'get_weather' or 'get_called_tools' beyond the resource difference, which prevents a perfect 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. It doesn't mention any context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name 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

Related 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/yeison-liscano/http_mcp'

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