Skip to main content
Glama
mcp-toolkit

mcp-toolkit

by Dongnb66

tc3_sign

Generate TC3-HMAC-SHA256 signed request headers, including Authorization, for Tencent Cloud API 3.0 calls. Accept credentials as parameters or from TC3_SECRET_ID/TC3_SECRET_KEY environment variables.

Instructions

生成腾讯云 API 3.0 的 TC3-HMAC-SHA256 签名请求头(含 Authorization)。密钥可入参或从环境变量 TC3_SECRET_ID / TC3_SECRET_KEY 读取,真实密钥不入日志。签名实现与官方公开测试向量逐字节一致。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payload": "<payload>"
    },
    "name": "tc3_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo接口域名,默认 sms.tencentcloudapi.com
actionNoAPI 动作,默认 SendSms
regionNo地域,默认 ap-guangzhou
payloadYes请求体 JSON 对象
serviceNo服务名,如 sms / cvm,默认 sms
versionNo版本号,默认 2021-01-11
secretIdNo腾讯云 SecretId,缺省读 TC3_SECRET_ID
secretKeyNo腾讯云 SecretKey,缺省读 TC3_SECRET_KEY
timestampNoUnix 秒级时间戳,缺省当前时间

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry the burden of behavioral disclosure. It does useful work: it says credentials can come from parameters or from TC3_SECRET_ID / TC3_SECRET_KEY environment variables, that real secrets are never written to logs, and that the implementation matches official public test vectors byte-for-byte, which signals determinism. It does not explicitly state that the tool performs only local computation with no network call, or what happens when credentials are missing.

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?

Three short sentences, front-loaded with the core purpose before credential handling and the fidelity claim. Little waste, though the test-vector sentence is more reassurance than actionable instruction.

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?

With nine parameters fully described in the schema and no output schema, the description covers purpose, credential sourcing, and secret-handling safety well. It could be stronger by describing the shape of the returned headers (for example, which header fields besides Authorization are produced) since no output schema exists to explain the return value.

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 description coverage is 100%, so all nine parameters are already documented with defaults and meaning. The description only restates the credential sourcing behavior (parameters vs. environment variables) that the schema already explains for secretId and secretKey, adding no new syntax or format detail.

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 names a specific verb and resource: generate TC3-HMAC-SHA256 signed request headers (including Authorization) for Tencent Cloud API 3.0. It names the exact algorithm and output artifact, so an agent knows precisely what the tool produces, and no sibling tool overlaps with this domain.

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?

Usage is implied: call this when you need signed headers for a Tencent Cloud API request. There is no explicit when-not guidance or mention of alternatives, and no statement about prerequisites such as needing valid credentials before calling, though the credential fallback note hints at setup requirements.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.