Skip to main content
Glama
Sign In
The Nothing

The Nothing

by Meador793
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Search (Nothing)

search
Read-onlyIdempotent

Returns an empty result list for any query, enabling AI workflows to prototype, demo, test, or dry-run without connecting to real data sources.

Instructions

Always returns an empty result list. It never searches any data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query. It will find nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the crucial behavioral fact beyond those annotations: the call is a guaranteed no-op returning an empty list. It does not mention error behavior for missing or odd query values, but for a no-op tool that is a minor gap.

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?

Two short sentences, zero filler, with the defining behavior (empty result) front-loaded. Nothing could be removed without losing information.

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 one-parameter no-op tool with full schema coverage and no output schema, the description supplies exactly the missing piece: the return value is always an empty list. An agent has everything needed to decide and call correctly.

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%, and the single query parameter is already documented in the schema as finding nothing. The description adds no format, length, or validation semantics for query, so the baseline of 3 applies.

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 specific and unambiguous effect: the tool 'always returns an empty result list' and 'never searches any data.' That is enough to tell it apart from a functional search or from siblings like fetch, though it does not explicitly contrast itself with those siblings by name.

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?

There is no guidance on when to use this tool versus fetch or pass_through, nor any statement of why an agent would ever call it (e.g., as a stub or placeholder). The agent is told what happens but not when the tool is appropriate.

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