Skip to main content
Glama
Tencent

Tencent Cloud COS MCP Server

Official
by Tencent

getCosConfig

Retrieve COS configuration settings for Tencent Cloud Object Storage via the MCP server, enabling direct access to storage and processing services without coding.

Instructions

获取COS配置, 腾讯云配置

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Inline handler function for the 'getCosConfig' tool. It masks the SecretId and SecretKey in the config if cosConfig exists, then returns the entire config as a JSON string in a text content block.
    server.tool('getCosConfig', '获取COS配置, 腾讯云配置', {}, async () => {
      if (config.cosConfig) {
        config.cosConfig.SecretId = maskSecret(config.cosConfig.SecretId);
        config.cosConfig.SecretKey = maskSecret(config.cosConfig.SecretKey);
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(config, null, 2),
          },
        ],
      };
    });
  • src/server.ts:68-82 (registration)
    Registration of the 'getCosConfig' tool using server.tool, with empty schema ({}), description '获取COS配置, 腾讯云配置', and inline handler.
    server.tool('getCosConfig', '获取COS配置, 腾讯云配置', {}, async () => {
      if (config.cosConfig) {
        config.cosConfig.SecretId = maskSecret(config.cosConfig.SecretId);
        config.cosConfig.SecretKey = maskSecret(config.cosConfig.SecretKey);
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(config, null, 2),
          },
        ],
      };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('get') without describing what the tool returns, whether it requires authentication, rate limits, or error conditions. For a tool with zero annotation coverage, this is insufficient behavioral context.

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

Conciseness4/5

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

The description is very concise with just two phrases ('获取COS配置, 腾讯云配置'). It's front-loaded with the core purpose. While efficient, it could be slightly more informative without losing conciseness.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what configuration data is returned, the format of the response, or any behavioral aspects. For a configuration retrieval tool, this leaves significant gaps in understanding how to use it effectively.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it correctly doesn't mention any parameters. Baseline 4 is appropriate for zero-parameter tools.

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?

The description '获取COS配置, 腾讯云配置' states the purpose (get COS configuration, Tencent Cloud configuration) but is vague about what specific configuration is retrieved. It distinguishes from siblings by focusing on COS configuration rather than operations like getObject or putObject, but lacks specificity about what configuration data is returned.

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. The description doesn't mention prerequisites, context for usage, or comparison with sibling tools like getBucket or getObject. It simply states what the tool does without indicating appropriate scenarios.

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

Related 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/Tencent/cos-mcp'

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