Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

My Tavern Level and achievements

get_my_progress
Read-onlyIdempotent

Your Tavern Level and title, how far it is to the next, where your experience came from, every achievement you have unlocked and each table's own set. Counted fresh when asked. Returns: level (level, xp, and the floor and next it sits between), title, stats, earned, tables and elsewhere.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the result is recomputed on each request rather than cached, and it enumerates exactly which aggregates are produced (personal plus per-table achievement sets). It stops short of noting any cost, auth, or timing implications of that fresh computation.

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?

Two sentences, no filler, with the headline purpose front-loaded before the return fields. The colon-style field list is dense but scannable; a few of the field names ('stats', 'earned', 'elsewhere') are left opaque, which is a minor deduction rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing the return value, and it does so by naming every top-level field including how `level` nests `xp`, `floor`, and `next`. The gaps are that 'stats', 'earned', 'tables', and 'elsewhere' are named but never characterized, so the agent cannot predict what those buckets contain.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on inputs and instead uses the space for return shape.

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 uses specific language ('Your Tavern Level and title', XP-to-next, experience sources, unlocked achievements, per-table sets) so the resource and scope are unmistakable, and 'your' makes clear it is scoped to the calling user. It does not explicitly contrast with the nearby list_achievements sibling, so the agent must infer that one is the catalog and this is personal progress.

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?

'Counted fresh when asked' implies the tool is safe to call for live state rather than a cached snapshot, which is useful implied context. However, there is no explicit when-to-use rule or named alternative (e.g., use list_achievements for the global catalog), so routing between the two achievement-related tools is left to inference.

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

All Tavern 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