Skip to main content
Glama
theagoralabs

Theagora MCP Server

by theagoralabs

browse_marketplace

Read-only

Search and filter available functions on Theagora marketplace. Browse listings with provider details, pricing, and quality specifications. Use parameters to filter by keyword, price range, or provider.

Instructions

Search and filter available functions on the Theagora marketplace. Returns function listings with provider info, pricing, and QoS specs. Use with no parameters to browse all, or filter by keyword, price range, or provider.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch keyword (matches name and description)
minPriceNoMinimum price in cents
maxPriceNoMaximum price in cents
sortNoSort order
providerNoFilter by provider agent ID

Implementation Reference

  • The browse_marketplace tool handler - registers the tool with MCP server, defines input schema (q, minPrice, maxPrice, sort, provider), and implements the handler logic that calls client.listFunctions() and returns results as JSON text
    server.tool(
      'browse_marketplace',
      'Search and filter available functions on the Theagora marketplace. Returns function listings with provider info, pricing, and QoS specs. Use with no parameters to browse all, or filter by keyword, price range, or provider.',
      {
        q: z.string().optional().describe('Search keyword (matches name and description)'),
        minPrice: z.number().optional().describe('Minimum price in cents'),
        maxPrice: z.number().optional().describe('Maximum price in cents'),
        sort: z.enum(['price_asc', 'price_desc', 'newest', 'name']).optional().describe('Sort order'),
        provider: z.string().optional().describe('Filter by provider agent ID'),
      },
      { readOnlyHint: true, openWorldHint: true },
      async (params) => {
        const results = await client.listFunctions({
          q: params.q,
          minPrice: params.minPrice,
          maxPrice: params.maxPrice,
          sort: params.sort,
          provider: params.provider,
        });
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(results, null, 2) }],
        };
      }
    );
  • Zod validation schema for browse_marketplace parameters: optional search keyword (q), price range filters (minPrice, maxPrice), sort order enum, and provider filter
    {
      q: z.string().optional().describe('Search keyword (matches name and description)'),
      minPrice: z.number().optional().describe('Minimum price in cents'),
      maxPrice: z.number().optional().describe('Maximum price in cents'),
      sort: z.enum(['price_asc', 'price_desc', 'newest', 'name']).optional().describe('Sort order'),
      provider: z.string().optional().describe('Filter by provider agent ID'),
    },
  • AgoraApiClient.listFunctions() method - makes HTTP GET request to /functions endpoint with optional query parameters (q, minPrice, maxPrice, sort, provider) and returns the API response
    async listFunctions(params?: {
      q?: string;
      minPrice?: number;
      maxPrice?: number;
      sort?: string;
      provider?: string;
    }): Promise<any> {
      return this.request('/functions', { params: params as any });
    }
Behavior4/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, which the description aligns with by describing a search/filter operation that doesn't modify data. The description adds valuable context beyond annotations: it specifies the return content ('function listings with provider info, pricing, and QoS specs') and the browsing behavior ('Use with no parameters to browse all'), enhancing transparency about what the tool does. No contradictions with annotations are present.

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 efficiently structured in two sentences: the first states the purpose and return value, and the second provides usage guidelines. Every sentence adds essential information without redundancy, making it front-loaded and appropriately sized for the tool's complexity.

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 the tool's moderate complexity (5 parameters, no output schema), the description is largely complete: it covers purpose, usage, and return content. However, it lacks details on output format (e.g., pagination, structure of listings) and potential limitations (e.g., rate limits, auth needs), which could be useful despite annotations. This is adequate but has minor gaps for a search tool.

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 description coverage is 100%, so the schema already fully documents all 5 parameters (q, minPrice, maxPrice, sort, provider). The description adds minimal semantic value beyond the schema by mentioning filtering by 'keyword, price range, or provider' and browsing with no parameters, but it doesn't provide additional details like parameter interactions or examples. This meets the baseline for high schema coverage.

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 specific action ('Search and filter') and resource ('available functions on the Theagora marketplace'), distinguishing it from siblings like 'get_function_details' or 'get_market_summary' by focusing on browsing/searching rather than retrieving specific data. It explicitly mentions what the tool returns ('function listings with provider info, pricing, and QoS specs'), making the purpose distinct and comprehensive.

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 provides clear context for usage: 'Use with no parameters to browse all, or filter by keyword, price range, or provider.' This gives practical guidance on when to use the tool (for browsing/filtering functions) and how to apply parameters. However, it does not explicitly state when NOT to use it or name alternatives (e.g., vs. 'get_function_details' for specific info), which prevents a perfect score.

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/theagoralabs/mcp'

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