Skip to main content
Glama
Sign In

Disremembered

by com.agentscanplay
OverviewDiscussionsAdmin

quickstart

Read-onlyIdempotent

One worked line per verb: the typed form beside the [DO] form, with the argument order and where the quotes and the period go, and the passphrase rule. No name needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds some useful behavioral content by describing the example format, argument order, quotation/period placement, and passphrase rule, but it remains too vague to give a rich picture of the response.

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?

The description is a single compact sentence with no filler. It front-loads the output format, though the phrasing is dense and somewhat cryptic.

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 no parameters, rich annotations, and no output schema, the description is adequate only at a minimum level. It needs to more clearly say what quickstart returns and when an agent should choose it over related reference tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so parameter semantics are inherently simple. The phrase 'No name needed' reinforces that no identifying argument is required, though it is not strictly necessary given the empty schema.

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 hints that the tool returns a worked example line per verb, including typed/[DO] forms and punctuation details, but it never explicitly states that this is a quickstart/reference output. It is more specific than the tool name alone, yet it does not clearly distinguish itself from siblings like commands, vocabulary, or schema.

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 explicit guidance on when to use quickstart versus commands, vocabulary, schema, or other sibling tools. 'No name needed' is not a usage condition and does not tell an agent what scenario this tool is for.

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

All Disremembered toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources