Folk Game

Folkgame — connector documentation

• MCP endpoint: https://folkgame.connectorbay.com/mcp
• REST API: POST https://folkgame.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://folkgame.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://folkgame.connectorbay.com/health · Tool schemas: https://folkgame.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/folkgame · agent@connectorbay.com

What Folkgame is for

A hand-curated reference for traditional folk & parlor games — rules, history, variants and DIY tips.

What it does

Folkgame is a fully local, hand-curated reference for traditional folk and parlor games. game_rules gives one game's full detail: equipment, objective, numbered how-to-play steps, winning condition, and an honest note on how much the rules vary by region and household. term_glossary defines terms specific to these games (squidger, squop, onesies, bilboquet, jackstraws, mikado, spillikin, ...) or lists them all. regional_variant gives a game's known regional and naming variants (bilboquet vs. kendama vs. balero, jacks vs. knucklebones vs. five stones). history_note gives a game's historical background, phrased qualitatively wherever exact dates are genuinely uncertain. find_game_for_group suggests games matching a player count and/or a plain-language age description. equipment_diy_tip explains how a game's equipment was traditionally homemade from ordinary materials. category_list groups every game into its type (Steady-Hand & Precision, Throw-and-Catch, String Figures, Contest & Dueling) with counts. beginner_tips gives starter tips and common early mistakes for a specific game. Keyless; fully local; zero upstream calls; nothing stored.

What it is not

Not an official product of, or affiliated with, any brand, league, publisher, or organization it may factually mention. Folkgame is a hand-curated reference and design tool, not a substitute for an official rulebook, certified instruction, or professional advice. Fully local, zero upstream calls, nothing stored.

Tools

Look Up a Game

game_rules — Full detail for one folk/parlor game: equipment, objective, numbered how-to-play steps, winning condition, difficulty, and an honest note on how much rules vary by region and household. Use for "how do you play conkers", "what's the goal of tiddlywinks". Args: name.

category_list — Every game grouped into its category (Steady-Hand & Precision, Throw-and-Catch, String Figures, Contest & Dueling) with a count and the games in each. Use for "what kinds of folk games do you cover".

term_glossary — Definitions of terms specific to these folk games — squidger, wink, squop, onesies, astragalus, bilboquet, kendama, jackstraws, mikado, spillikin, and general folk-game vocabulary like 'house rule'. Use for "what's a squidger", "what does onesies mean in jacks". Args: term.

History & Variants

history_note — A game's historical background — origins, approximate era, and how it evolved — phrased qualitatively wherever exact dates or first records are genuinely uncertain. Use for "how old is the game of jacks", "where does cat's cradle come from". Args: name.

regional_variant — A game's known regional, historical, or naming variants — e.g. bilboquet vs. kendama vs. balero, or knucklebones vs. jacks vs. five stones. These folk games were never standardized, so this list is illustrative, not exhaustive. Use for "what's the difference between spillikins and pick-up sticks", "regional names for cup and ball". Args: name.

Play & Make

find_game_for_group — Suggests games that fit a given player count and/or a plain-language age description, matched against each game's typical group size and age notes. Use for "what folk game works for 4 kids", "a game for one adult who's home alone", "something for a mixed-age family gathering". Args: player_count, age_range.

equipment_diy_tip — How a game's equipment was traditionally made at home from ordinary household or found materials — no purchase required. Use for "how do you make your own conkers", "DIY pick-up sticks", "homemade cup-and-ball toy". Args: name.

beginner_tips — A short list of starter tips for a specific game — what to focus on first, common early mistakes to avoid. Use for "tips for a beginner at conkers", "how do I get better at jacks". Args: name.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/folkgame/support

Folkgame — Privacy Policy

Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Folkgame is. Folkgame is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated reference for traditional folk & parlor games — rules, history, variants and DIY tips. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call, the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Folkgame is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Folkgame — Terms of Service

Effective 25 September 2026. These terms govern use of the Folkgame connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Folkgame is a fully local, hand-curated reference for traditional folk and parlor games.
2. A reference, not professional advice. Folkgame is an independent reference and hobby/game-design tool, not affiliated with or endorsed by any brand, organization, league, or publisher it may factually mention. It does not provide legal, financial, medical, or safety-certification advice, and is not a substitute for supervised instruction where real physical risk is involved.
3. Content varies. Rules, terminology and conventions described here reflect commonly-cited general practice; local house rules, regional variants, and official governing-body rulebooks may differ.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/folkgame

Folk Game support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://folkgame.connectorbay.com/mcp
• REST API: https://folkgame.connectorbay.com/openapi.json
• Live status: https://folkgame.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Folk Game never asks for them.