Skip to main content
Glama

Excellent Reference (free)

Search Excellent's public pages

search_excellent_pages
Read-onlyIdempotent

Search Excellent's published pages: feature pages (what each part of the product does), comparison pages (Excellent vs another events or private-dining platform, with where each one wins and the date the comparison was last reviewed), the blog, and guides (how to connect Claude, with 15 things to ask it). Returns up to 5 pages with their URL and the page's own summary text. No account needed.

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_excellent_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional: only one kind of page.
queryYesWhat to look up, in plain words (e.g. "deposit schedule", "banquet event order", "Tripleseat").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "feature",
      -  "comparison",
      -  "blog"
      -]New value: +[
      +  "feature",
      +  "comparison",
      +  "blog",
      +  "guide"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (which already declare read-only, idempotent, non-destructive, closed-world), the description adds genuinely useful behavior: the result cap of 5 pages, the returned fields (URL plus the page's own summary text), and the absence of an auth requirement. It does not mention ranking or what happens with zero matches, which keeps it from a 5.

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?

Front-loaded with the verb and scope, then return behavior and access requirement, so the most decision-relevant facts come first. The opening sentence is a long parenthetical-heavy run-on, but each clause carries real distinguishing information rather than filler.

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 two-parameter read-only search with full schema coverage, rich annotations, and no output schema, the description covers scope, content types, return shape, result cap, and auth needs. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so the schema already documents both params, but the description adds meaning the enum lacks: each kind value is glossed (feature pages explain product parts, comparisons note winners and a last-reviewed date, guides cover Claude connection). That lets an agent choose the right 'kind' without guessing.

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 gives a specific verb (search) and resource (Excellent's published pages), then enumerates the four page families with what each contains, so an agent knows exactly what corpus is being searched. It stops short of naming how it differs from the sibling excellent_help, which arguably covers overlapping 'how to connect Claude' guide material.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it's clear this is for looking up public marketing/doc content, and 'No account needed' signals low-friction access. However, there is no explicit when-to-use framing against excellent_help or start_excellent_workspace, and no statement of when this tool is the wrong choice (e.g. for account-specific data).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources