Skip to main content
Glama

list_services

List available marketplace services with pricing, quality scores, and capabilities. Filter by category, quality score, price, or capability to find services meeting your requirements.

Instructions

List all available services on the AgentDesk marketplace. Returns service catalog with pricing, quality scores, and capabilities. Filter by category, minimum quality score, maximum price, or capability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category: quality_assurance, web_scraping, realtime_data, document_generation, text_processing
min_scoreNoMinimum quality score (0-100)
max_priceNoMaximum price per call in USD
capabilityNoFilter by capability keyword

Implementation Reference

  • src/index.ts:92-113 (registration)
    Registration of the 'list_services' tool via server.tool() on the McpServer instance.
    server.tool(
      'list_services',
      'List all available services on the AgentDesk marketplace. Returns service catalog with pricing, quality scores, and capabilities. Filter by category, minimum quality score, maximum price, or capability.',
      {
        category: z.string().optional().describe('Filter by category: quality_assurance, web_scraping, realtime_data, document_generation, text_processing'),
        min_score: z.number().optional().describe('Minimum quality score (0-100)'),
        max_price: z.number().optional().describe('Maximum price per call in USD'),
        capability: z.string().optional().describe('Filter by capability keyword'),
      },
      safeAsyncTool(async ({ category, min_score, max_price, capability }) => {
        const params = new URLSearchParams()
        if (category) params.set('category', category)
        if (min_score !== undefined) params.set('min_score', String(min_score))
        if (max_price !== undefined) params.set('max_price', String(max_price))
        if (capability) params.set('capability', capability)
    
        const url = `${AGENTDESK_API}/api/v1/services${params.toString() ? '?' + params.toString() : ''}`
        const res = await fetch(url)
        if (!res.ok) throw new Error(`API error: ${res.status} ${res.statusText}`)
        return await res.json()
      })
    )
  • Handler function for list_services: builds query params, fetches from AgentDesk API /api/v1/services, and returns JSON response.
    safeAsyncTool(async ({ category, min_score, max_price, capability }) => {
      const params = new URLSearchParams()
      if (category) params.set('category', category)
      if (min_score !== undefined) params.set('min_score', String(min_score))
      if (max_price !== undefined) params.set('max_price', String(max_price))
      if (capability) params.set('capability', capability)
    
      const url = `${AGENTDESK_API}/api/v1/services${params.toString() ? '?' + params.toString() : ''}`
      const res = await fetch(url)
      if (!res.ok) throw new Error(`API error: ${res.status} ${res.statusText}`)
      return await res.json()
    })
  • Input schema for list_services: optional category, min_score, max_price, and capability filters.
    {
      category: z.string().optional().describe('Filter by category: quality_assurance, web_scraping, realtime_data, document_generation, text_processing'),
      min_score: z.number().optional().describe('Minimum quality score (0-100)'),
      max_price: z.number().optional().describe('Maximum price per call in USD'),
      capability: z.string().optional().describe('Filter by capability keyword'),
Behavior3/5

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

No annotations are provided, so the description must disclose behaviors; it mentions returning service details but omits pagination, rate limits, or any restrictions. It is adequate but not thorough.

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 two sentences with no wasted words: first sentence states purpose, second adds return content and filters. Extremely concise.

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?

For a simple listing tool with no output schema and no annotations, the description covers the basics but lacks details on pagination, error handling, or output structure, which might be needed.

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?

Input schema has 100% description coverage, and the description merely lists the filter names without adding meaning beyond what the schema already provides, so it meets the baseline.

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 verb 'List' and resource 'available services on the AgentDesk marketplace', and distinguishes from siblings by focusing on browsing the catalog, while sibling tools execute or review services.

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 browsing services with filters, but does not explicitly state when to use this tool versus alternatives like execute_service or review tools, nor provides exclusions or conditions.

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/Rih0z/agentdesk-mcp'

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