Skip to main content
Glama

list_matches

List matched suppliers and products for a procurement intent, showing match score and price to compare and select a supplier for negotiation.

Instructions

查看意图匹配到的商品和商家。返回列表含 match_id、商家名称、价格、匹配度评分。选中商家后用 select_and_negotiate 开始议价。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intent_idYes意图 ID

Implementation Reference

  • Tool registration/definition for 'list_matches' including name, description, and inputSchema requiring intent_id
      name: 'list_matches',
      description: '查看意图匹配到的商品和商家。返回列表含 match_id、商家名称、价格、匹配度评分。选中商家后用 select_and_negotiate 开始议价。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          intent_id: { type: 'number', description: '意图 ID' },
        },
        required: ['intent_id'],
      },
    },
  • Handler routing for 'list_matches': parses args with IntentIdSchema and calls client.listMatches(intent_id)
    case 'list_matches': {
      const p = S.IntentIdSchema.parse(args);
      result = await client.listMatches(p.intent_id);
      break;
  • Actual API client method listMatches(intentId) that sends GET request to /acap/v1/intents/{intentId}/matches
    async listMatches(intentId: number) {
      return this.request('GET', `/acap/v1/intents/${intentId}/matches`);
    }
  • Zod schema IntentIdSchema used for parsing the intent_id parameter in list_matches handler
    export const IntentIdSchema = z.object({
      intent_id: z.number().int().positive(),
    });
  • src/index.ts:124-124 (registration)
    Feature group registration including 'list_matches' in the 'intent' tool group
    'get_sourcing_status', 'list_matches', 'list_responses',
Behavior3/5

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

No annotations are provided. The description lacks details on behavior like error handling, authentication, or side effects. However, the tool is read-only, so the absence of negative information is acceptable but not exemplary.

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?

Two sentences with no waste: first states purpose and return fields, second gives next step. Efficient and well-structured.

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?

Lacks output schema but lists return fields. Also mentions the next step. Missing details on error conditions or pagination, but sufficient for a simple list 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 coverage is 100% for the single parameter. The description does not add new semantic meaning beyond the schema; it merely restates the purpose of the parameter in context.

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 it lists products and merchants matched to an intent, specifying the return fields (match_id, merchant name, price, match score) and explicitly names the next step (select_and_negotiate), distinguishing it from sibling tools.

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 explicit usage flow: use this to view matches, then use select_and_negotiate. It does not explicitly state when not to use, but the guidance is clear and actionable.

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/ggqshuai-hub/a2amarket-mcp-server'

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