Skip to main content
Glama

IKANGAI Vibe Support

What people have built with AI

list_showcase
Read-only

Real games, rebuilt apps and tools that people made mainly with AI coding tools: who built it and with what, and a summary. Use it when the person wants ideas, asks what is possible, or doubts they can build something. Each entry rests on the builder's own account and another source; the projects are not tested by us. Call get_notice with an id for how it was built and what was hard.

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

Input Schema

NameRequiredDescriptionDefault
toolNoOnly what applies to this tool. Leave out for everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only and non-open-world traits, so the description correctly spends its words elsewhere: it discloses provenance ('rests on the builder's own account and another source') and a caveat that 'the projects are not tested by us.' That trust framing is genuinely beyond structured data. It does not mention pagination or result size, keeping it from a 5.

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 what the tool lists, then usage triggers, then the provenance caveat, then the follow-up call. Four sentences each carrying distinct information. Slightly prose-like but nothing is redundant.

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?

A simple read-only list tool with one optional parameter and no output schema, so the description's job is mostly framing: what an entry contains, how trustworthy it is, and where to get depth. All of that is present. Result shape and volume are left unstated, a minor gap for a browse tool.

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 enum parameter is documented in-schema, so the baseline applies. The phrase 'who built it and with what' loosely gestures at the tool filter but adds no syntax or filtering semantics. No compensation is needed given full schema documentation.

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 names the concrete resource — real games, rebuilt apps and tools made with AI coding tools — and states what each entry carries (builder, tool used, summary). The verb is only implicit from the name 'list', but an agent can tell this is a showcase browser rather than a notice lookup. It does not explicitly contrast with list_notices or list_toolbox, so it falls short of a 5.

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

Usage Guidelines4/5

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

Gives concrete trigger conditions: 'when the person wants ideas, asks what is possible, or doubts they can build something.' It also names the natural follow-up ('Call get_notice with an id'), which routes the agent to the detail tool. No explicit when-not guidance or sibling exclusions are offered.

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.

Resources