Skip to main content
Glama

TavernFinder

by io.github.bmachado86
OverviewDiscussionsAdmin

register_user

Create a Tavern Finder account for the person you are helping, and get a reusable access token for it. Use the account immediately — booking and creating events work right away. STORE THE ACCESS TOKEN and reuse it for this person every time; do not call this again for someone you already registered. You also get a claim link: give it to the person so they can take ownership, set their own email and password, and see their bookings on the website. Only pass an email if the person actually gave you one — otherwise leave it out and they will set it when they claim.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFirst name
emailNoOptional. The person's real email, only if they gave you one. Omit it rather than inventing one — they set it when claiming.
localeNoPreferred locale: 'pt' | 'en' | 'es' (default 'pt')
lastNameYesLast name
passwordYesPassword, minimum 8 characters. Generate a strong random one; the person replaces it when they claim.
tosAcceptedYesMust be true. Confirms the user agreed to https://tavernfinder.com/terms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Email address (will receive a verification mail)"New value: +"Optional. The person's real email, only if they gave you one. Omit it rather than inventing one — they set it when claiming."
    • changedInput schema / properties / password / description
      Previous value: -"Password, minimum 8 characters"New value: +"Password, minimum 8 characters. Generate a strong random one; the person replaces it when they claim."
    • changedInput schema / required
      Previous value: -[
-  "email",
-  "password",
-  "name",
-  "lastName",
-  "tosAccepted"
-]New value: +[
+  "password",
+  "name",
+  "lastName",
+  "tosAccepted"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and succeeds: it reveals side effects (account creation, token and claim link issued), immediate availability, non-repeatability, and the email-passing safety rule. This is rich behavioral context beyond the schema.

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?

Each sentence adds necessary operational information, with the core action front-loaded. Despite its length, it avoids filler and uses emphasis to highlight the token-storage requirement.

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, but the description names the two return artifacts (access token and claim link) and explains how both should be used. Nothing an agent needs to invoke this 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 baseline is 3. The description adds meaning beyond the schema by explaining when to pass or omit email and that the password should be a generated temporary value replaced at claim time.

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 and resource: 'Create a Tavern Finder account... and get a reusable access token.' This clearly differentiates the tool from event-centric siblings like create_event and search_events.

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

Usage Guidelines5/5

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

Provides explicit operational guidance: use the account immediately, store and reuse the token, and 'do not call this again for someone you already registered.' It also instructs when to omit email, making the expected invocation context unambiguous.

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

All TavernFinder toolsInspect
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