Skip to main content
Glama

IKANGAI AI News

Projects built with AI

built_with_ai
Read-onlyIdempotent

Things people built with AI coding tools such as Claude Code or Codex: games, clones of known products, apps, tools. For ideas for your own or your user's work. Each has what was built, how, with which tools, what to take from it, and the author's own sentence saying AI built it. Newest first. That AI built a project is its author's claim; nobody tested it.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this kind of project. clone rebuilds or replaces a known product.
toolNoOnly projects built with this AI tool or model, such as Claude Code.
limitNo
queryNoWords to look for. All must match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description still adds real behavioral context: results are newest first, each record carries what was built, how, which tools, takeaways and the author's own sentence. The caveat that the AI-built claim is unverified and untested is a genuine trust signal not present in any structured field.

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 definition is front-loaded with what the tool returns, followed by the result shape and then the provenance caveat, and every sentence carries information. Phrasing is slightly fragmentary ('games, clones of known products, apps, tools') but nothing is wasted or buried.

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

Completeness3/5

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

With four optional parameters and no output schema, the description does compensate by describing the fields of each record and the ordering, which is the main gap it needed to fill. However, it says nothing about result counts, empty results, or how limit interacts with the default, leaving pagination behavior undefined.

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 75%, so the schema already documents kind, tool, limit and query, including the enum values and the 'clone' clarification. The description adds only indirect hints ('with which tools', 'games, clones') and no new meaning about how filters combine, so the baseline 3 applies.

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 states a specific resource - projects built with AI coding tools - and enumerates the facets ('games, clones of known products, apps, tools') that map directly onto the kind enum. It names example tools (Claude Code, Codex) to anchor the domain, but never contrasts itself with siblings like latest_stories or search_stories, so the agent must infer the distinction.

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?

'For ideas for your own or your user's work' implies the use case but gives no explicit trigger conditions, no exclusions, and no named alternative for when a different sibling tool should be used instead. Usage is implied rather than prescribed.

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