Skip to main content
Glama
ConsentirDev

BuyICT MCP Server

by ConsentirDev

list_marketplaces

Retrieve available procurement marketplaces and types to identify suitable channels for Australian Government ICT opportunities through the BuyICT platform.

Instructions

Get list of available marketplaces/procurement types

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the list_marketplaces tool that retrieves marketplaces from the ServiceNow client and returns them as formatted JSON.
    case 'list_marketplaces': {
      const marketplaces = snClient.getMarketplaces();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(marketplaces, null, 2),
          },
        ],
      };
    }
  • src/index.ts:102-109 (registration)
    Tool registration including name, description, and input schema (empty object).
    {
      name: 'list_marketplaces',
      description: 'Get list of available marketplaces/procurement types',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    }
  • Helper method in ServiceNowClient that returns the configured list of marketplaces.
     * Get list of marketplaces
     */
    getMarketplaces(): Marketplace[] {
      return this.config.marketplaces;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get list') but doesn't mention any behavioral traits such as authentication needs, rate limits, response format, or potential side effects. This is inadequate for a tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It could be slightly more structured by front-loading key details, but it's appropriately concise for a simple tool.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't explain the return values or behavioral context, which is a gap since there's no output schema to compensate.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter details, but with no parameters, this is acceptable, and the baseline score is 4 as per the rules for 0-param tools.

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 the verb ('Get') and resource ('list of available marketplaces/procurement types'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_opportunities' or 'get_opportunity_details', which prevents a perfect score.

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 no guidance on when to use this tool versus alternatives like 'search_opportunities' or 'get_opportunity_details'. It lacks context about prerequisites, timing, or exclusions, leaving the agent without usage direction.

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/ConsentirDev/buyict.mcp'

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