Skip to main content
Glama

browse-spines-underground

Browse 23 curated products from the Underground Cultural District — 13 free, 10 paid. Use optional product ID for single product details.

Instructions

Browse Spine's Underground catalog — 23 curated products from Underground Cultural District. 13 free, 10 paid ($1.99–$4.99 USDC on Base). Tools, poetry, philosophy, music theory, digital experiences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idNoOptional product ID for single product detail. Omit for full catalog.

Implementation Reference

  • index.js:28-40 (registration)
    Tool registration in ListToolsRequestSchema handler: defines tool name 'browse-spines-underground', description, and inputSchema with optional product_id parameter.
    {
      name: 'browse-spines-underground',
      description: "Browse Spine's Underground catalog — 23 curated products from Underground Cultural District. 13 free, 10 paid ($1.99–$4.99 USDC on Base). Tools, poetry, philosophy, music theory, digital experiences.",
      inputSchema: {
        type: 'object',
        properties: {
          product_id: {
            type: 'string',
            description: 'Optional product ID for single product detail. Omit for full catalog.',
          },
        },
      },
    },
  • Input schema for browse-spines-underground: accepts optional product_id string. When omitted, returns full catalog.
      inputSchema: {
        type: 'object',
        properties: {
          product_id: {
            type: 'string',
            description: 'Optional product ID for single product detail. Omit for full catalog.',
          },
        },
      },
    },
  • Handler logic for browse-spines-underground: calls fetchJSON to GET /catalog (full catalog) or /catalog/{product_id} (single product detail), returns JSON response as text content.
    case 'browse-spines-underground': {
      const path = args.product_id ? `/catalog/${args.product_id}` : '/catalog';
      const data = await fetchJSON(path);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Helper function fetchJSON used by the handler: makes fetch request to the API base, handles 402 payment challenges, returns parsed JSON.
    async function fetchJSON(path) {
      const res = await fetch(`${API_BASE}${path}`);
      if (res.status === 402) {
        const paymentHeader = res.headers.get('PAYMENT-REQUIRED');
        return {
          status: 402,
          message: 'Payment required. This product costs USDC on Base via x402 protocol.',
          payment_challenge: paymentHeader,
          instructions: 'Decode the PAYMENT-REQUIRED header (base64 JSON) to get payment details. Sign a USDC transfer and re-request with PAYMENT-SIGNATURE header.',
        };
      }
      return res.json();
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the catalog content but does not mention behavioral traits such as being read-only, safety, or any authentication/rate limit requirements. For a read operation, this is adequate but not exhaustive.

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?

The description is a single, well-structured sentence with essential information front-loaded. Every part adds value, and there is no redundancy or verbosity.

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?

Given no output schema, the description provides sufficient context about return content (catalog items, categories, pricing). It is complete for a simple browse tool, though it could hint at output format or pagination if present.

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 schema already describes the single optional parameter clearly. The tool description adds contextual information about the catalog count and pricing but does not enhance parameter semantics 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?

The description clearly states the tool's function: browsing the Spine's Underground catalog. It specifies the scope (23 curated products), categories, and pricing, distinguishing it from sibling tools like buy, search, or verify.

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 description implicitly guides usage by mentioning optional product_id for single product detail, suggesting when to omit for full catalog. However, it does not explicitly state when to use this tool over siblings like search-spines-underground.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lisamaraventano-spine/spines-underground'

If you have feedback or need assistance with the MCP directory API, please join our Discord server