Skip to main content
Glama

SafeSellAI

从这里开始

start_here

SafeSellAI 接入引导:返回文字版上手步骤(试查品牌词 → 批量排查 → 免费店铺体检)。支持 MCP Apps 的客户端会同时渲染欢迎面板。适用场景:刚接入、不知道先做什么时调用。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_here"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does clarify the return shape (text steps, plus a welcome panel only for MCP Apps-capable clients), which is genuinely useful, but it says nothing about whether the call is read-only, costs balance, or requires authentication — relevant given get_balance and check_* siblings.

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 clauses, front-loaded with what is returned before the usage scenario, and each sentence carries information. The leading 'SafeSellAI 接入引导' label is partly redundant with the title, a small amount of waste in an otherwise tight definition.

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

Completeness3/5

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

For a zero-parameter entry-point tool with no output schema, the description covers what comes back and when to call it, which is most of what is needed. It is still silent on cost, permissions, and whether calling it has any side effects, so an agent cannot fully predict the outcome.

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 takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. Nothing in the description misleads about inputs.

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

Purpose4/5

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

States a specific action and result: it returns text onboarding steps (试查品牌词 → 批量排查 → 免费店铺体检), which makes its role distinct from the actual check_* tools it references. The one gap is that it never explicitly says 'this tool performs no checks itself', leaving sibling differentiation implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition — call it when newly onboarded or unsure what to do first — which is exactly the decision point an agent needs. It stops short of any exclusion (e.g. 'do not call after you already know the next step'), but the positive guidance is clear and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources