Skip to main content
Glama

trends

Discover what agents are searching for across the agent economy. Identify emerging trends in agent queries to inform your services.

Instructions

Get what agents are searching for

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:17-32 (registration)
    The 'trends' tool is registered in the ListToolsRequestSchema handler as one of the free tools with description 'Get what agents are searching for' and an empty input schema.
    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:34-70 (handler)
    The CallToolRequestSchema handler processes the 'trends' tool by checking it against the freeEndpoints map on line 37, then calling fetch(BASE_URL + '/trends') on lines 40-43 and returning the JSON response as text content.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      const freeEndpoints = { stats: '/stats', quality: '/quality', protocols: '/protocols', prices: '/prices', trends: '/trends' };
    
      if (freeEndpoints[name]) {
        const resp = await fetch(BASE_URL + freeEndpoints[name]);
        const data = await resp.json();
        return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
      }
    
      if (name === 'agent_check') {
        const resp = await fetch(`${BASE_URL}/agent/check?wallet=${args.wallet}${args.category ? '&category=' + args.category : ''}`);
        const data = await resp.json();
        return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
      }
    
      if (name === 'submit') {
        const resp = await fetch(`${BASE_URL}/submit`, { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify(args) });
        const data = await resp.json();
        return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
      }
    
      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)
        }]
      };
    });
  • The freeEndpoints mapping defines 'trends' -> '/trends' API endpoint path, used by the handler to route the tool call to the correct backend URL.
    const freeEndpoints = { stats: '/stats', quality: '/quality', protocols: '/protocols', prices: '/prices', trends: '/trends' };
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as read-only status, authentication requirements, or rate limits. For a tool with no parameters, it should at least hint at what the output represents.

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

Conciseness2/5

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

The single sentence is concise but under-specified. It does not earn its place because it lacks crucial details for effective agent use.

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

Completeness1/5

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

Given no input schema, no output schema, and no annotations, the description is highly incomplete. It does not explain what the tool returns, what 'agents' refers to, or any other contextual information.

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?

With zero parameters, schema coverage is effectively 100%. The description adds the meaning 'what agents are searching for', which is useful context beyond the empty schema. Baseline of 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get what agents are searching for' provides a verb and resource but is vague. 'Agents' is ambiguous, and it doesn't clearly distinguish from siblings like 'discover' or 'find'. It avoids tautology but lacks specificity.

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?

No guidance is given on when to use this tool versus alternatives like 'discover' or 'find'. The description does not mention context or exclusions.

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