Skip to main content
Glama
hyen43

Model Context Protocol Server

by hyen43

example_tool

Process messages to extend Claude's capabilities through custom tools in the Model Context Protocol Server.

Instructions

An example tool that processes messages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to process

Implementation Reference

  • The main handler function for the example_tool. It takes an input with a message field and returns the message prefixed with 'Processed: '.
    async execute(input: ExampleInput) {
      return `Processed: ${input.message}`;
    }
  • Input schema definition using Zod for validation. Defines 'message' as a required string field.
    schema = {
      message: {
        type: z.string(),
        description: "Message to process",
      },
    };
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 only states 'processes messages' without detailing traits like side effects, permissions, rate limits, or output format, leaving significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence with no wasted words, making it appropriately concise. However, it lacks front-loaded critical information, such as specific actions or context, which slightly reduces its effectiveness.

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. It fails to explain what 'processes' means, the tool's behavior, or return values, making it inadequate for a tool with one parameter and no structured support.

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 'message' parameter documented as 'Message to process'. The description adds no additional meaning beyond this, such as examples or constraints, so it meets the baseline score for high schema coverage without compensating value.

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

Purpose3/5

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

The description states 'processes messages', which provides a vague purpose without specifying what processing entails (e.g., filtering, analyzing, transforming). It does not differentiate from sibling tools like 'weather' or 'weather_api', leaving ambiguity about its role in the toolset.

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, such as the sibling tools 'weather' and 'weather_api'. The description lacks context, prerequisites, or exclusions, offering no help in tool selection.

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/hyen43/mcpServer'

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