Skip to main content
Glama

delete_hosted_strategy

Delete a hosted strategy to stop automatic responses to intents in that category.

Instructions

删除托管策略。删除后不再自动响应该品类的意图。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strategy_idYes策略 ID

Implementation Reference

  • The actual implementation of deleteHostedStrategy in the AcapClient class. It sends a DELETE request to '/acap/v1/hosted/strategies/{strategyId}' to delete a hosted strategy.
    async deleteHostedStrategy(strategyId: number) {
      return this.request('DELETE', `/acap/v1/hosted/strategies/${strategyId}`);
    }
  • The tool registration/schema definition for 'delete_hosted_strategy', including its inputSchema which requires a strategy_id (number).
    {
      name: 'delete_hosted_strategy',
      description: '删除托管策略。删除后不再自动响应该品类的意图。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          strategy_id: { type: 'number', description: '策略 ID' },
        },
        required: ['strategy_id'],
      },
    },
  • src/index.ts:147-149 (registration)
    Registration of 'delete_hosted_strategy' in the 'hosted_strategy' feature group, which controls whether this tool is enabled.
    hosted_strategy: [
      'set_hosted_strategy', 'list_hosted_strategies', 'delete_hosted_strategy',
    ],
  • The switch-case handler in the CallToolRequestSchema handler that parses the strategy_id argument and calls client.deleteHostedStrategy(strategy_id).
    case 'delete_hosted_strategy': {
      const { strategy_id } = args as { strategy_id: number };
      result = await client.deleteHostedStrategy(strategy_id);
      break;
    }
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the direct effect (no longer auto-respond), but lacks details on idempotency, permissions, reversibility, or error handling.

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 short sentences, front-loaded with action and consequence. No extraneous information.

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?

For a simple delete tool with one parameter and no output schema, the description adequately explains the purpose and effect. Minor gap: no mention of return value or error conditions.

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% (one parameter fully described). The description does not add extra meaning to the parameter beyond what the schema provides.

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 action (delete the hosted strategy) and the consequence (no longer automatically respond to intents). It distinguishes from siblings like 'set_hosted_strategy' and 'list_hosted_strategies'.

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 stopping auto-response to a category, but does not explicitly state when to use this tool versus alternatives, nor provides exclusion criteria.

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