Skip to main content
Glama

Funko Me level rules: XP sources and the level curve (public)

ic_funko_levels
Read-only

The Funko Me level rules: every XP source with its rate and cap, and the 10-level curve with each level's name. No auth required; this is the rules table, nobody's progress (for one member's level call ic_funko_progress). Levels never go down. Only records the site reads itself earn XP: a Luma check-in (not an RSVP), a verified welcome quest (not a claimed one), a published log entry with a link (not a draft), commits from a linked GitHub (up to 50 a week), hosting a Luma event, using a floor resource (headset, print, transcription), making the figure, and weeks of membership. The membership ring earns no XP. Each source carries how, the action that earns it, so you can tell your human what to do next. Args: {}. Returns: { ok, version, xp_sources[{ signal, xp, per, how }], levels[{ level, at_xp, name }], rules[] }. No auth required.

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": "ic_funko_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description goes well beyond them: it discloses the full set of XP-qualifying actions and their non-qualifying counterparts (check-in not RSVP, verified not claimed quest, published not draft), the 50/week GitHub cap, the explicit rule that levels never decrease, and that the membership ring earns nothing. That is exactly the kind of rule-level context an agent needs to explain results to a human, and nothing contradicts the annotations.

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?

The core purpose and the sibling hand-off are front-loaded in the first two sentences, and the XP enumeration is genuinely informative rather than filler. It loses a point for restating 'No auth required' twice and for listing XP sources at length when the return payload already contains an `xp_sources` array with `how` fields.

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?

For a read-only, zero-argument rules lookup, everything an agent needs is present: scope, no-auth status, the semantics of the returned structures (`signal`, `xp`, `per`, `how`, `level`, `at_xp`, `name`), and the monotonic-level rule. The output schema exists, so the description need not restate return values, and it correctly leaves them at a high-level shape.

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?

There are zero parameters, which is the baseline-4 case; the description confirms this with 'Args: {}' so the agent knows the call takes no arguments. No further parameter meaning is possible or needed.

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?

The description opens with a specific verb-and-resource statement: it returns the XP source table with rates and caps, plus the 10-level curve with names. It also names the sibling it is not ('nobody's progress ... for one member's level call ic_funko_progress'), so the agent can separate it from a progress lookup without opening a schema.

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?

Explicit when-to-use is given ('the rules table, nobody's progress') and the alternative for the other case is named outright (`ic_funko_progress`). It also states no auth is required, removing a common pre-call blocker.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.