Skip to main content
Glama
Sign In
The Nothing

The Nothing

by Meador793
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Do Nothing

nothing
Read-onlyIdempotent

Acknowledges steps that require no action and returns '...' as a placeholder for future database or dataset operations.

Instructions

Deliberately does nothing and returns '...'. Use it to acknowledge a step that needs no action, or as a placeholder where a real database/dataset operation may live someday.

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": "nothing"
  }
}

Input Schema

NameRequiredDescriptionDefault
anythingNoOptional. Anything at all. It will be politely ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare that the tool is read-only, non-open-world, idempotent, and non-destructive. The description adds useful behavioral context beyond that by specifying the return value '...' and explaining the placeholder/no-op semantics.

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 two tightly written sentences with the core behavior front-loaded. Every sentence earns its place by stating both what the tool does and when to use it.

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

Completeness5/5

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

For a trivial no-op tool with rich safety annotations, a fully documented optional parameter, and no output schema, the description is complete. It covers purpose, return value, and intended usage without leaving meaningful gaps.

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 and already explains that the single optional parameter is politely ignored. The description does not add parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a precise behavior: it deliberately does nothing and returns '...'. This clearly distinguishes it from active siblings like search and fetch, though it does not explicitly name or contrast with the nearby pass_through tool.

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

Usage Guidelines4/5

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

It gives clear usage contexts: acknowledging a step that needs no action, or acting as a placeholder for a future real operation. It does not state when not to use it or name explicit alternatives, but the intended use is unambiguous.

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