Skip to main content
Glama

list_responses

Retrieve active seller quotations for a given procurement intent. Returns list with prices, quantities, delivery dates, and seller information.

Instructions

查看卖家主动报价。返回列表含报价金额、数量、交期、卖家信息。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intent_idYes意图 ID

Implementation Reference

  • Handler case in the main tool dispatch that calls client.listResponses(p.intent_id) with parsed IntentIdSchema.
    case 'list_responses': {
      const p = S.IntentIdSchema.parse(args);
      result = await client.listResponses(p.intent_id);
      break;
  • The low-level API client method listResponses that sends a GET request to /acap/v1/intents/{intentId}/responses.
    async listResponses(intentId: number) {
      return this.request('GET', `/acap/v1/intents/${intentId}/responses`);
    }
  • The Zod schema IntentIdSchema used for input validation: requires intent_id as a positive integer.
    export const IntentIdSchema = z.object({
      intent_id: z.number().int().positive(),
    });
  • src/index.ts:357-366 (registration)
    Tool registration block defining the 'list_responses' tool with name, description, and inputSchema.
      name: 'list_responses',
      description: '查看卖家主动报价。返回列表含报价金额、数量、交期、卖家信息。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          intent_id: { type: 'number', description: '意图 ID' },
        },
        required: ['intent_id'],
      },
    },
  • src/index.ts:122-125 (registration)
    Tool grouping registration listing 'list_responses' under the 'intent' category.
    intent: [
      'publish_intent', 'get_intent_status', 'cancel_intent',
      'get_sourcing_status', 'list_matches', 'list_responses',
    ],
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It implies a read operation but does not explicitly state that it is non-destructive, nor does it mention authentication or rate limits. The description is insufficient to inform the agent of side effects or safety.

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 short sentences with no redundant information. It efficiently conveys the purpose and output fields.

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 list tool with one parameter and no output schema, the description covers the basic purpose and output fields. However, it lacks details on pagination, ordering, or possible empty results, which would improve completeness.

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?

The input schema has 100% coverage with a description for the only parameter (intent_id). The tool description does not add any additional meaning or constraints beyond what the schema 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 tool's purpose: viewing seller's active quotes. It specifies the verb (查看/view), resource (卖家主动报价/seller's active quotes), and the return format (列表含报价金额、数量、交期、卖家信息). This is distinct from sibling tools like list_supply_products or list_conversations.

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 provided on when to use this tool versus alternatives, nor any prerequisites or conditions. The description only states what the tool does, leaving the agent to infer context.

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