Skip to main content
Glama
safiyu

ctxtest

hello-world

Generate a hello greeting for a specified name. Enter a name to receive a personalized hello message.

Instructions

A simple hello world tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name to say hello to

Implementation Reference

  • src/index.ts:28-28 (registration)
    Registration of the 'hello-world' tool name and schema in the ListToolsRequestSchema handler.
    name: "hello-world",
  • Input schema for 'hello-world' tool: requires a 'name' string property.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "The name to say hello to",
        },
      },
      required: ["name"],
    },
  • Handler logic for the 'hello-world' tool call: reads name argument and returns a greeting string.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      if (request.params.name === "hello-world") {
        const name = String(request.params.arguments?.name || "World");
        return {
          content: [
            {
              type: "text",
              text: `Hello, ${name}! This is the ctxtest MCP server.`,
            },
          ],
        };
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'simple hello world tool' without disclosing traits like output format, side effects, or required permissions.

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

Conciseness3/5

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

The description is very short (one sentence) and has no waste, but it is under-specified. It could be expanded slightly to improve clarity.

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 simplicity (1 required param, no output schema), the description is minimally adequate. However, it lacks detail about the return value or what the tool actually does with the name.

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 100% (the 'name' parameter has a description). The description adds no additional meaning beyond the schema's 'The name to say hello to'. Baseline 3 is appropriate.

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 says 'A simple hello world tool', which implies a greeting but does not explicitly state the verb (e.g., 'Says hello') or the resource. It is somewhat vague but not a tautology.

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 on when to use this tool vs. the sibling 'stat'. There is no mention of context or alternatives.

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/safiyu/ctxnest'

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