Skip to main content
Glama
Sign In

UXKIN

by io.github.uxkin
OverviewDiscussionsAdmin

Open a collection

get_collection
Read-onlyIdempotent

Get the items in one of the person's saved collections on uxkin.com (app screens, whole apps and website designs, newest first), with images and links. Pass the collection's name as the person said it (case doesn't matter) or its id from list_collections. Use the items as the references the person chose for the task.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection": "<collection>"
    },
    "name": "get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collectionYesThe collection's name, e.g. "Checkout ideas", or its id.

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
countYesHow many items it has.
itemsYesSaved items, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: results are ordered newest first, items carry images and links, and lookup is case-insensitive whether by name or id.

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?

Three sentences, front-loaded with what is returned before the how-to-call detail. No filler, though the closing sentence about using items as references is somewhat soft guidance rather than strictly necessary.

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 single-parameter read tool with an output schema and rich annotations, nothing an agent needs is missing: input form, ordering, content type, and the relationship to list_collections are all covered, and the output schema handles return values.

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?

Schema coverage is 100% and the single parameter already has an example, so the baseline is 3. The description earns an extra point by specifying that the name should be passed 'as the person said it' and that casing is irrelevant, which is semantics the schema does not state.

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 verb and resource ('Get the items in one of the person's saved collections'), names the domain (uxkin.com), and defines the content scope (app screens, whole apps, website designs). It is clearly distinguishable from list_collections, which enumerates collections rather than their contents.

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 a concrete selection context ('Use the items as the references the person chose for the task') and points to list_collections as the way to obtain an id. It stops short of an explicit when-not-to-use or a statement of when this beats find_ui_references/find_ui_materials.

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

All UXKIN toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources