Skip to main content
Glama
Sign In
Underground Cultural District MCP Server

Underground Cultural District MCP Server

by lisamaraventano-spine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search-underground

Find products from Underground shops using keyword search, with optional filters for category and price limit.

Instructions

Search products across all Underground shops by keyword. Optionally filter by category or max price.

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": "search-underground"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch keywords
categoryNoFilter by category (optional)
price_maxNoMaximum price in USD (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. It lacks details on whether it's read-only, pagination, rate limits, or result caching.

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?

Two concise sentences with no redundancy. All information is front-loaded.

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?

Adequate for basic understanding but missing behavioral details and usage context for a search tool with three parameters and no output schema.

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 covers 100% of parameters with descriptions. The description adds only 'by keyword' and 'optional', which is marginal extra meaning.

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?

The verb 'search' and resource 'products across all Underground shops' are specific. It distinguishes from siblings like 'browse-underground' and 'buy-from-underground'.

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?

The description implies usage for keyword search with optional filters but does not explicitly state when to use or avoid this tool versus alternatives like 'browse-underground'.

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