Excellent Reference (free)

Start a sample Excellent workspace

start_excellent_workspace

Creates a new Excellent workspace filled with sample data (a fictional restaurant group with two venues, bookings, proposals, invoices, staff training and marketing drafts) and returns a one-time link for the person you are helping. Opening the link while signed in to Excellent, or after creating a login there, makes the workspace theirs. Nobody can use it before then, and an unclaimed workspace is deleted when its link expires after 7 days. Takes no arguments and no personal data. At most 3 a day per address.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations (which only say it is a non-read-only, non-destructive, non-idempotent write): it discloses the claim flow, that the workspace is unusable until claimed, that unclaimed workspaces are deleted after 7 days, that no personal data is required, and a rate limit of 3 per day per address. These are exactly the operational details an agent needs before calling.

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 primary action is front-loaded in the first clause, then lifecycle and limits follow in tight sentences. Four sentences, each carrying distinct information (contents, return value, claim mechanics, expiry, rate limit) with no repetition.

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?

There is no output schema, and the description compensates by describing the return value (a one-time link) and what the caller must do with it. Combined with the expiry and rate-limit notes, nothing critical is missing for correct invocation.

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?

Zero parameters, so the baseline is 4, and the description reinforces this by explicitly stating 'Takes no arguments and no personal data', which prevents an agent from hunting for hidden inputs. No meaningful semantics remain to be added.

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?

States a specific verb ('Creates') and resource ('a new Excellent workspace') and even enumerates the seeded sample data. This is unmistakably distinct from the siblings excellent_help and search_excellent_pages, which are read/informational tools.

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?

The framing ('returns a one-time link for the person you are helping') makes the use case clear: provisioning a demo workspace for a user. It does not explicitly state when not to use it or name an alternative path, but the siblings are so far removed that no real ambiguity exists.

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

All Excellent Reference (free) tools Inspect

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

Need Help?