Skip to main content
Glama
Sign In
uex-market-mcp

uex-market-mcp

by jbillochon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Find UEX items

find_items
Read-onlyIdempotent

Look up UEX catalog items by partial or misspelled name to retrieve exact names and IDs for accurate marketplace listing searches.

Instructions

Look up items in the UEX catalog by name (typo tolerant) to get their exact names and ids before searching listings.

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": {
      "query": "<query>"
    },
    "name": "find_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesPart of an item name.
categoryNoOptional UEX category or section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds one genuinely extra behavioral trait ('typo tolerant' matching), but says nothing about result size caps, ranking/ordering, or behavior when many items match.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the verb, matching behavior, and downstream purpose front-loaded. No filler or repetition of structured fields beyond what's needed for orientation.

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?

For a read-only, three-parameter lookup with no output schema, the description conveys what comes back (exact names and ids) and why. Minor gaps around result ordering and the limit behavior keep it from being fully complete.

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 67%, with query and category documented and limit carrying only default/range constraints. The description restates the name-based query but never mentions the limit cap or the category filter, so it adds little beyond the schema.

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 (look up items in the UEX catalog by name) plus the payoff (exact names and ids). It also positions itself against search_listings by framing this as the prerequisite lookup, so an agent can distinguish it from siblings without reading the schema.

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?

The phrase 'before searching listings' gives clear sequencing guidance and implies when this tool is the right first step. It does not name search_listings directly or state explicit exclusions/edge cases (e.g., ambiguous results), so it falls short of a full when/when-not statement.

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

Deploy Server

Other Tools