Skip to main content
Glama

SafeSellAI

guest_info

查询当前匿名试用的额度、免费店铺体检剩余次数与任务进度,不扣额度。适用场景:接入后先看还剩多少免费量、任务做到哪一步。

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": "guest_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 load, and it does disclose one important trait: the call does not consume quota ('不扣额度'). It also implies no authentication is needed by scoping to anonymous trial. However, it says nothing about rate limits, error behavior when no trial exists, or whether 'task progress' requires an ambient session/context given the zero-parameter schema.

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 tight clauses: what is returned plus the no-cost guarantee, then the scenario. No filler, and the primary scope is front-loaded before the usage hint.

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 no-parameter read tool with no output schema, the definition covers what is returned (quota, remaining free audits, task progress) and the cost profile. The only real gap is how 'task progress' is scoped without any identifier parameter, which an agent may wonder about before calling.

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 the baseline is 4; there is no parameter meaning for the description to add or omit.

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?

The description names specific resources with a clear verb: current anonymous trial quota, remaining free store-audit count, and task progress. It implicitly separates itself from the paid-balance sibling by scoping to '匿名试用' (anonymous trial), but it never names get_balance or any alternative, so the differentiation must be inferred.

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?

It gives an explicit usage scenario: right after integration, check how much free quota remains and what step the task has reached. That is a concrete when-to-use cue, but there is no when-not-to-use guidance and no pointer to the sibling that handles logged-in account balances.

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