MCP tool reference · #346 of 563 by publishers
guide
Exposed by 10 servers from 10 publishers, read from the live servers by the Serverdex check; most of them sit in Developer Tools; 10% of them take a customer_type parameter; the most-starred is FetchSandbox (1 stars).
guide(…)Parameters
share = % of the 10 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| customer_type | string | 10% | 0% | mineral-processing | dark-proteins | alloys; omit for the list |
| hints | object | 10% | 0% | Optional caller-supplied overrides. Each field short-circuits the corresponding detection step. |
| intent | string | 10% | 100% | The developer's free-form prompt as they typed it. Don't pre-process or shorten — the router benefits from the full phrasing (capture timing, geo cues, failure |
| name | — | 10% | 0% | — |
| section | — | 10% | 0% | — |
| sections | array | 10% | 0% | — |
| slug | string | 10% | 100% | The guide slug, such as 'startup-credits' |
| template | string | 10% | 0% | openmm-stability (dark-proteins stage 1 OpenMM script); returns the script text |
| topic | string | 10% | 0% | optional: what you need ("refund a payment") — returns only the docs sections that answer it, as direct .md links |
Source: the input schema each server returns for guide, aggregated over the 10 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with guide
10 of 10 · 10 publishers · 10 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes guide |
|---|---|---|---|---|---|---|
| 1 | FetchSandboxfetchsandbox · Developer Tools | fetchsandbox | Developer Tools | 1 | yes | ROUTE a symptom to the provider behaviour that explains it. Use this when the user names a provider or a domain (payments, email, auth, SMS, subscriptions) and you need to know what that provider ACTUALLY does — not what its docs say, and not what can be inferred from reading the integration code. Reading the code tells you what your app does with a field. It cannot tell you what the field MEANS a |
| 2 | Ticker Scouttickerscout · Other | tickerscout | Other | 1 | yes | Start here if unsure. How Ticker Scout's tools fit together: what a record is versus a period, the period syntax every period argument accepts, units and currency, how figures are cited and linked to sec.gov, which tool answers common questions, and the standard figures (with the words get_figure and compare_companies accept for each). No arguments. |
| 3 | Megido: niche, competitor and traffic research on sites with observed revenuemegido-io · Search & Web | megido-io | Search & Web | — | yes | Return the client guide in full, as Markdown: what the corpus is and what it cannot tell, how to read every field and band, what each call costs and spends, the recommended order of work, recipes for common questions and how to report results to your user. Free. Read it at the start of a session when the server instructions are not in your context, and whenever you are unsure how to read a field o |
| 4 | Colorado Startupscolorado-startups · Games & Sports | colorado-startups | Games & Sports | — | yes | One founder guide from coloradostartups.org/guides/: its title, summary and full answer, with a link. Find the slug with search, type guide. |
| 5 | Gemmeingemmeinhq · Developer Tools | gemmeinhq | Developer Tools | — | yes | Returns the Gemmein build guide (llms.txt): the packaged contract — what code calls, matching the installed SDK. Useful before building an app on Gemmein, moving an existing app onto it, or deciding whether an app fits. The guide opens with two doors — starting from an idea with nothing built yet, or already holding an app — and both lead to the same fit assessment: the in-scope map, what Gemmein |
| 6 | EntryLibentrylib · Content & Publishing | entrylib | Content & Publishing | — | yes | How to write a claimset: a skill of the claimset package by name (claimset-from-paper for an author's own paper, claimset-submit for any submission, claimset-lab, claimset-revise, claimset-review), or name='specification' for the Claimset specification, whole or one numbered section (section='3.4'). Without a name: the list. Write a claimset only from these texts, not from |
| 7 | AI Stock League (Korea) - trading.pe.krtradingpekr · Finance | tradingpekr | Finance | — | yes | 가입 절차, 한국어 전용 규칙, 커뮤니티 API, 예측 리그 규칙이 담긴 안내문을 읽는다. 처음 연결했으면 먼저 읽는다. (Participation guide.) |
| 8 | Arcade.funtheguysaccount · Search & Web | theguysaccount | Search & Web | — | yes | Read this first. What a build must be, how to start from a working game, how to add licensed assets, how to check a build and how to publish. Pass `sections` to get only some. |
| 9 | MDEngineforcefieldsilicon · AI & Agents | forcefieldsilicon | AI & Agents | — | yes | No key needed. Without customer_type: the list of guides (one line each), the start page and how to get a key. With customer_type (mineral-processing | dark-proteins | alloys): the full guide, which says what to supply, what runs, what comes back and what it costs. With template (openmm-stability): the script text of that template, ready to save and submit. |
| 10 | Corroboratewangkant · Education & Reference | wangkant | Education & Reference | — | yes | Read first: the rules, what counts as evidence, how review is scored, and limits. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.