Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DELPHI_BASE_URLNoSet to any Discourse forum base URL to use the server against that forum instead of Chief Delphi.https://www.chiefdelphi.com
DELPHI_CACHE_DIRNoDirectory for on-disk response caching. Delete the directory to force a refetch; there is no cache-off switch.<repo>/.cache
DELPHI_USER_AGENTNoThe user agent token that robots.txt rules are matched against.delphi-mcp/0.1 (+read-only Discourse client)
DELPHI_MIN_INTERVAL_MSNoMinimum interval in milliseconds between serialized requests. Raise it if you see 403 / 429 / 503.350
DELPHI_REQUEST_TIMEOUT_MSNoPer-request timeout in milliseconds.20000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
cd_categoriesA

List every Chief Delphi (chiefdelphi.com) category and subcategory with its numeric id and slug. Call this first when you need to scope a search or browse to a forum area such as Technical, Competition or Announcements. Read-only, no login. Returns ids usable in cd_topics/cd_find category=.

cd_topicsA

Browse a page of Chief Delphi topic listings: newest (mode=latest), newly created (mode=new), or most-engaged (mode=top with a period). Optionally scope to one category. Use this to survey what is being discussed rather than to look for a specific phrase (use cd_find for that). Each row carries the topic id, slug, category id, post count, view count and last activity; feed ids to cd_raw or cd_topic.

cd_findA

Find Chief Delphi topics matching keywords. Chief Delphi robots.txt disallows /search, so this does NOT call the forum search API: it pulls topic listings (mode/period/category/page window), matches tokens against titles, tags and excerpts, ranks the hits, then fetches /raw for the top with_body candidates to confirm the phrase inside the thread and report which posts matched. Coverage is the listing window you ask for, so the default mode=auto pools both most-engaged (top) and most-recent (latest) topics. An empty result means "not in this window", not "the forum has no such thread" — widen pages= or change mode. Good targets: game rumor/prediction threads, rule clarifications, strategy and build threads, event discussion.

cd_topicA

Read a Chief Delphi thread with per-post metadata: author, user title, timestamp, like count, which post is replied to, post id, deleted/hidden flags. Threads render in ~20-post windows; jump with at_post= (exact, gap-safe) or page= (page 2 starts at post 21). Discourse pads a window to ~20 live posts, so a thread containing deleted posts can repeat one boundary post between consecutive pages — prefer at_post for exact continuation. Use format="json" to reason over structured fields, format="text" (default) to read the discussion. For a cheap bulk read of a long thread use cd_raw instead.

cd_rawA

Fetch a Chief Delphi thread as plain Discourse markdown (the /raw endpoint) — the cheapest way to read a whole discussion, with author and timestamp headers per post and image references left as upload:// tokens. Read only part of a long thread with start_post/end_post to keep the reply small.

cd_userA

Look up a Chief Delphi account profile: trust level, titles, join date, last seen, last posted, profile views, time read, badge count, location, website, bio and profile fields (FRC/FTC team number, rookie year, roles). Useful for judging how much weight to give a forum claim. Anonymous Discourse does not expose post counts or likes received, and it does not list that user posts — see the note in the output for why.

cd_watchA

Report what changed in a Chief Delphi listing since the previous cd_watch call on the same scope: brand-new topics, plus topics whose post or view counts moved, with deltas. The first call records a baseline and lists nothing new; call it again later to get the diff. Made for following an ongoing discussion — game rumor and prediction threads during a season, a build thread you are tracking, or one category during kickoff week — without re-reading the same listings. State persists in .state/ (separate from the disposable cache), is keyed per scope, and reset starts over.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a distinct role: cd_categories for id discovery, cd_topics for surveying listings, cd_find for keyword search, cd_topic/cd_raw for reading threads (structured vs cheap bulk), cd_user for profiles, and cd_watch for diffs over time. The descriptions explicitly resolve the closest overlaps, e.g. cd_find tells the agent to use cd_topics for general surveying and warns its search is listing-window based, and cd_topic points to cd_raw for bulk reads. No two tools appear interchangeable.

Naming Consistency4/5

All tools share a predictable cd_ prefix plus a short snake_case identifier, and the plural/singular split (cd_topics listing vs cd_topic thread) is meaningful rather than accidental. Minor deviation: it mixes noun-style names (cd_categories, cd_user) with verb-style names (cd_find, cd_watch), so the naming is consistent in form but not strictly verb_noun.

Tool Count5/5

Seven tools is well-scoped for a read-only forum client: discovery, listing, search, two read modes, profiles, and polling. Every tool covers a distinct workflow step and none feels redundant or bolted on.

Completeness4/5

The surface covers the full read lifecycle of a forum—find a category, survey listings, search, read a thread cheaply or richly, inspect a user, and track changes over time. Gaps are minor and partly inherent to anonymous Discourse: there is no way to list a given user's posts, no direct post-id fetch, and no write operations (reasonably out of scope for a login-less server), but agents can work around these via thread reads.