Skip to main content
Glama

unsubscribe_intent

Cancel an active intent subscription to stop receiving updates and end participation in related procurement activities using the subscription ID.

Instructions

取消意图订阅。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_idYes订阅 ID(subscribe_intent 返回)

Implementation Reference

  • Handler case for 'unsubscribe_intent' in the CallToolRequestSchema handler. Parses args with UnsubscribeSchema, then calls client.unsubscribeIntent(p.subscription_id).
    case 'unsubscribe_intent': {
      const p = S.UnsubscribeSchema.parse(args);
      result = await client.unsubscribeIntent(p.subscription_id);
      break;
  • Zod schema for unsubscribe_intent input validation. Requires 'subscription_id' as a positive integer.
    export const UnsubscribeSchema = z.object({
      subscription_id: z.number().int().positive(),
    });
  • src/index.ts:610-620 (registration)
    Tool registration metadata in the tools array. Defines name, description, and inputSchema for unsubscribe_intent.
    {
      name: 'unsubscribe_intent',
      description: '取消意图订阅。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          subscription_id: { type: 'number', description: '订阅 ID(subscribe_intent 返回)' },
        },
        required: ['subscription_id'],
      },
    },
  • Client method that sends a DELETE request to /acap/v1/subscriptions/{subscriptionId} to unsubscribe.
    async unsubscribeIntent(subscriptionId: number) {
      return this.request('DELETE', `/acap/v1/subscriptions/${subscriptionId}`);
    }
  • src/index.ts:144-144 (registration)
    unsubscribe_intent listed under the 'subscription' feature group.
    'subscribe_intent', 'unsubscribe_intent', 'list_subscriptions',
Behavior2/5

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

No annotations provided. Description lacks behavioral details: effects of unsubscription, idempotency, permissions, or side effects. Agent has little to infer safety or outcomes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single short sentence is concise but under-specified. It restates the tool name without adding value. Structure is minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks context for a mutation tool: no output schema, no mention of idempotency, success/failure signals, or prerequisites. Agent may misjudge when to invoke.

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 covers parameter fully (100% coverage) with description of 'subscription_id'. The tool description adds no extra meaning; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states '取消意图订阅' (cancel intent subscription), matching the tool name. It's clear but doesn't distinguish from sibling 'cancel_intent', which might cancel an intent itself. Minimal elaboration.

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 on when to use this tool vs alternatives like 'cancel_intent'. No context on prerequisites or exclusions.

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