Skip to main content
Glama

list_hosted_strategies

Retrieve all hosted trading strategies with strategy ID, category, and pricing rules to review and manage procurement and negotiation configurations.

Instructions

列出已设置的托管策略。返回策略列表含 strategy_id、品类、报价规则。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:147-149 (registration)
    Tool 'list_hosted_strategies' is registered in the 'hosted_strategy' group alongside 'set_hosted_strategy' and 'delete_hosted_strategy'.
    hosted_strategy: [
      'set_hosted_strategy', 'list_hosted_strategies', 'delete_hosted_strategy',
    ],
  • Input schema definition for 'list_hosted_strategies': description and empty input schema (no parameters required).
    {
      name: 'list_hosted_strategies',
      description: '列出已设置的托管策略。返回策略列表含 strategy_id、品类、报价规则。',
      inputSchema: { type: 'object' as const, properties: {} },
    },
  • Handler case for 'list_hosted_strategies': calls client.listHostedStrategies() and returns the result.
    case 'list_hosted_strategies': {
      result = await client.listHostedStrategies();
      break;
    }
  • ACAP client method listHostedStrategies() making a GET request to /acap/v1/hosted/strategies.
    async listHostedStrategies() {
      return this.request('GET', '/acap/v1/hosted/strategies');
    }
Behavior3/5

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

The description discloses the read-only nature implicitly and lists return fields, but with no annotations, it does not provide additional behavioral context such as security, rate limits, or potential side effects.

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 concise, consisting of two sentences that front-load the purpose and then detail the output. No unnecessary 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 list tool with no parameters or output schema, the description adequately covers purpose and return fields. It could mention potential sorting or pagination but is sufficient.

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?

With zero parameters and 100% schema coverage, the description adds no parameter info, which is appropriate. Baseline for 0 params is 4.

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 lists hosted strategies and specifies the return fields (strategy_id, category, quotation rules). This distinguishes it from sibling tools like set_hosted_strategy and delete_hosted_strategy.

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. While the purpose implies it is for listing, there is no explicit when/when-not or mention of other tools.

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