Skip to main content
Glama
Sign In
The Nothing

The Nothing

by Meador793
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Pass Through

pass_through
Read-onlyIdempotent

Returns any JSON payload unchanged to simulate data operations, so AI workflows can be prototyped or dry-run without real data sources and later swapped to a live implementation.

Instructions

Returns the payload exactly as received (identity). This is Mr. Decoupler's seam: route data operations through it today, swap in a real implementation later without changing the AI-facing contract.

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": {
      "payload": "<payload>"
    },
    "name": "pass_through"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesAny JSON value (object, array, string, number, boolean or null).
operationNoOptional label for the intended operation, e.g. 'query', 'insert', 'transform'. Not executed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds the genuinely important behavioral fact that this is a stub that will later be swapped for a real implementation — so the agent knows nothing is persisted or executed. It stops short of stating that the `operation` field has no effect, leaving that only to the schema.

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?

Two sentences, front-loaded with the core behavior, no filler about return values. The second sentence leans on internal jargon ("Mr. Decoupler's seam") that costs a few words without helping an agent act, but it does convey the placeholder intent.

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?

With only 2 fully documented params, complete annotations, and no output schema, little is required — and the identity behavior plus stub status are covered. What's missing is any statement of when this tool should be chosen over its siblings, which for a deliberately inert tool is exactly the decision an agent needs help with.

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%, including the note that `operation` is "Not executed," so the schema already carries full parameter meaning. The description mentions no parameters at all; baseline 3 applies when the schema does all the work.

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?

"Returns the payload exactly as received (identity)" is a specific verb+resource statement that unambiguously describes the transformation applied. The second sentence clarifies intent (placeholder seam) but never distinguishes this tool from the siblings nothing/search/fetch, so an agent must infer the routing on its own.

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?

"Route data operations through it today" is developer-facing migration advice rather than agent-facing when-to-use guidance, and no alternative or exclusion is named. Worse, the phrasing suggests data operations will be performed, while the schema says the operation label is "Not executed" — the guidance points the agent in a slightly wrong direction.

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