Skip to main content
Glama

find

Describe what you need in plain English to discover relevant services from a curated index of over 1450 options.

Instructions

Intent-based discovery - describe what you need in plain English (costs $0.02 USDC on Base)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYesDescribe what you need

Implementation Reference

  • Input schema for the 'find' tool: requires an 'intent' string property. This defines the tool's input validation.
    { name: 'find', description: 'Intent-based discovery - describe what you need in plain English (costs $0.02 USDC on Base)', inputSchema: { type: 'object', properties: { intent: { type: 'string', description: 'Describe what you need' } }, required: ['intent'] } },
  • server.js:17-32 (registration)
    Tool registration in ListToolsRequestSchema handler. Tool named 'find' with description and inputSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        { name: 'stats', description: 'Get ecosystem statistics - 1,551 services across x402, MPP, and Lightning protocols', inputSchema: { type: 'object', properties: {} } },
        { name: 'quality', description: 'Get service quality grades - we test 70 services weekly and grade them A-F', inputSchema: { type: 'object', properties: {} } },
        { name: 'protocols', description: 'Get cross-protocol breakdown: x402 vs MPP vs L402/Lightning', inputSchema: { type: 'object', properties: {} } },
        { name: 'prices', description: 'Get market pricing trends across the agent economy', inputSchema: { type: 'object', properties: {} } },
        { name: 'trends', description: 'Get what agents are searching for', inputSchema: { type: 'object', properties: {} } },
        { name: 'discover', description: 'Search for x402/MPP/Lightning services by keyword (costs $0.01 USDC on Base)', inputSchema: { type: 'object', properties: { query: { type: 'string', description: 'Search keyword' } }, required: ['query'] } },
        { name: 'find', description: 'Intent-based discovery - describe what you need in plain English (costs $0.02 USDC on Base)', inputSchema: { type: 'object', properties: { intent: { type: 'string', description: 'Describe what you need' } }, required: ['intent'] } },
        { name: 'compare', description: 'Compare services side by side with quality grades and recommendations (costs $0.02 USDC on Base)', inputSchema: { type: 'object', properties: { capability: { type: 'string', description: 'Service capability to compare' }, sort_by: { type: 'string', enum: ['quality', 'price', 'speed'], description: 'Sort order' } }, required: ['capability'] } },
        { name: 'market_report', description: 'Full market intelligence report - top categories, pricing trends, opportunities (costs $1.00 USDC)', inputSchema: { type: 'object', properties: {} } },
        { name: 'market_opportunity', description: 'Gap analysis - underserved niches and overpriced categories to undercut (costs $0.50 USDC)', inputSchema: { type: 'object', properties: {} } },
        { name: 'submit', description: 'Submit your x402/MPP/Lightning service for free indexing', inputSchema: { type: 'object', properties: { url: { type: 'string', description: 'Your service URL' }, name: { type: 'string', description: 'Service name' }, description: { type: 'string', description: 'What your service does' } }, required: ['url'] } },
        { name: 'agent_check', description: 'Check if an agent wallet is registered and authorized (FREE)', inputSchema: { type: 'object', properties: { wallet: { type: 'string', description: 'Agent wallet address (0x...)' }, category: { type: 'string', description: 'Service category to check authorization for' } }, required: ['wallet'] } },
      ]
    }));
  • server.js:57-69 (handler)
    Handler logic for the 'find' tool. Since it's a paid endpoint (find: null in paidEndpoints), it returns an x402 payment required message with the endpoint '/find'.
    const paidEndpoints = { discover: `/discover?q=${encodeURIComponent(args.query || '')}`, find: null, compare: null, market_report: '/market/report', market_opportunity: '/market/opportunity' };
    
    return {
      content: [{
        type: 'text',
        text: JSON.stringify({
          message: `This tool requires x402 payment (USDC on Base). Call ${BASE_URL}/${name.replace('_', '/')} directly with an x402-enabled client.`,
          endpoint: BASE_URL + (name === 'discover' ? `/discover?q=${encodeURIComponent(args.query || '')}` : name === 'find' ? '/find' : name === 'compare' ? '/compare' : `/${name.replace('_', '/')}`),
          payment_required: true,
          how_to_pay: 'npm install @x402/fetch && see https://github.com/cinderwright-ai/cinderwright-api/blob/main/DEMO.md'
        }, null, 2)
      }]
    };
Behavior2/5

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

The description mentions a cost of $0.02 USDC, which is a behavioral trait, but it does not disclose whether the tool is read-only, destructive, or any side effects. With no annotations provided, the description carries the full burden, and it fails to describe key behavioral aspects beyond cost.

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 description is a single, concise sentence with no wasted words. However, it lacks structure such as front-loading the most critical information (e.g., cost first) and could be slightly improved in readability.

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

Completeness2/5

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

Given the tool has one parameter, no output schema, and no annotations, the description is incomplete. It does not explain what the tool returns, how results are presented, or how it differs from the sibling 'discover.' This lack of context hampers an agent's ability to use it appropriately.

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% with the 'intent' parameter described as 'Describe what you need.' The description adds 'in plain English,' which clarifies the input format but does not add substantial meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states 'Intent-based discovery' and 'describe what you need in plain English,' which effectively conveys the tool's purpose as a natural language search tool. However, the sibling tool 'discover' could overlap, and the description doesn't distinguish them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides basic guidance to 'describe what you need' and mentions cost, but it does not specify when to use this tool versus alternatives like 'discover,' nor does it indicate when not to use it. No exclusions or context for selection are provided.

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/cinderwright-ai/cinderwright-api'

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