hello-world-mcp

Hello World Tool

helloWorld

Greets the user with a custom hello message. Provide a name to personalize the greeting, or leave it empty to greet the world.

Instructions

A simple hello world tool that greets the user

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "helloWorld"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Name to greet, defaults to 'world'	world

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'greets the user' without stating whether this is a safe read-only operation, what the output looks like, or any side effects. The description is essentially a tautology of the tool's name and title, offering no extra behavioral context.

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, short sentence with no unnecessary words. It is front-loaded with the tool's purpose and earns its place, perfectly sized for a trivial hello-world tool.

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 and complete schema, the description adequately conveys the main function. However, there is no output schema, so the description could have mentioned the format of the greeting or any return value. For a greeting tool, this is implied but not explicitly stated, leaving a minor gap.

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 fully describes the only parameter (name) with a clear description and default value, so schema coverage is 100%. The description adds nothing beyond the schema, which is acceptable per the baseline guideline of scoring 3 when the schema covers parameters.

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

Purpose5/5

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

The description clearly states the tool greets the user with a specific verb ('greets') and resource ('the user'). There are no siblings to distinguish from, so the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage context is implied by the name and description ('hello world' is obviously used for greeting), but there is no explicit guidance on when to use this tool versus alternatives. Since no alternatives exist, the lack of comparison is acceptable, but the description still doesn't provide explicit context such as typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

helloWorldA