Skip to main content
Glama

SafeSellAI

optimize_ai

AI 改写 Listing。适用场景:标题/描述命中风险词后自动改写。匿名试用暂未开放。

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": {
      "items": "<items>"
    },
    "name": "optimize_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say whether the rewrite mutates stored data or merely returns suggestions, whether it consumes credits/balance, how long it takes, or what the caller receives. Only the anonymous-trial restriction is genuine behavioral disclosure.

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 action and immediately followed by the trigger scenario. No filler, though the brevity is partly under-specification rather than discipline.

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?

With no annotations, no output schema, and an undocumented nested parameter, the description should explain what a rewrite returns (new title? full listing? per-item results?) and how the 'items' batch maps to output. Neither is covered, leaving an agent unable to predict the call's result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, 'items', an array of objects with an optional 'title' string and minItems 1, and schema description coverage is 0%. The description says nothing about 'items' — whether each element is one listing to rewrite, what happens when 'title' is omitted, or whether batching is allowed — so it fails to compensate for the coverage gap.

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 a concrete action and its target: an AI that rewrites a Listing, plus the trigger condition (risk words hit in title/description). That is far more specific than a restatement of the name, but it never distinguishes itself by name from the check_* siblings that presumably surface the risk words in the first place.

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?

'适用场景:标题/描述命中风险词后自动改写' tells the agent exactly when to reach for this tool, and '匿名试用暂未开放' adds an availability precondition an agent could otherwise trip over. There are no explicit when-not conditions and no named alternative, so it stops short of a 5.

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