Skip to main content
Glama

List every Funko Me unlock and what earns it (public)

ic_funko_catalog
Read-only

The full catalog of things a Funko Me figure can earn — animation clips, props, skins, stages — with the condition that unlocks each one. No auth required; this is the rules table, not anybody's progress. Use it to explain to a human WHY something is locked, or to show what is worth doing on the floor. An item with no requires is granted to every signed-in member. Conditions read as { signal, gte } (a measurable: commits this week, events checked in, days of tenure), { minTier } (a membership ring) or { minLevel } (a Funko Me level; ic_funko_levels has the rules). Every any lists alternatives: the first one met grants it. For one member's actual progress against these, call ic_funko_progress. Args: { kind?: 'clip'|'prop'|'skin'|'stage'|'capability' }. Returns: { ok, count, items[{ id, kind, label, blurb?, rarity, requires?, asset? }] }. 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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional filter — return only unlocks of this kind.

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

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral substance: no auth required, the distinction between rules and per-member state, the default when `requires` is absent (granted to every signed-in member), and how conditions are encoded ({ signal, gte }, { minTier }, { minLevel }) including that `any` lists alternatives and the first met grants the item.

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?

Front-loaded with purpose, then usage, then data semantics, with zero filler sentences. The only blemish is 'No auth required' appearing twice (opening and closing), a small redundancy in an otherwise dense paragraph.

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?

Despite an output schema already existing, the description still usefully names the return shape and fields, and it resolves the genuinely ambiguous part — how `requires` conditions should be interpreted and what an empty `requires` means. Nothing an agent needs to call or interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single `kind` enum is fully documented in the schema, including its role as an optional filter. The description's 'Args: { kind?: clip|prop|skin|stage|capability }' essentially repeats the schema rather than adding format or behavioral nuance, so the baseline 3 applies.

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 resource (the full catalog of Funko Me earnables) and what it carries (the unlock condition per item), and explicitly contrasts itself with progress-tracking: 'this is the rules table, not anybody's progress.' An agent can distinguish it from ic_funko_progress without opening either 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?

Gives concrete when-to-use cases ('explain to a human WHY something is locked', 'show what is worth doing on the floor') and names the alternative with its selecting condition: 'For one member's actual progress against these, call ic_funko_progress.' Nothing 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.