Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Search the help center

help_search
Read-onlyIdempotent

Search SimianX's help center when the user asks how something works on the website (live analysis, deep analysis, autopilots, auto digest, points, plans, account). Returns titles, summaries and the page URL; read the full article with help_read. Without q it lists the articles.

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

Input Schema

NameRequiredDescriptionDefault
qNoWhat the user asked about, in their words
limitNoRows, up to 10 (default 5)
localeNoArticle language, e.g. en, zh-CN, de (default: the user's)
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered; the description adds the genuinely useful part – the return payload ('titles, summaries and the page URL') and the no-query listing behavior. It stops short of noting result-count or empty-result behavior, so it is strong but not complete.

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 sentences, front-loaded with the trigger and resource, then the return value and the escape hatch to help_read. Every clause carries information; no filler.

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 no output schema, the description compensates by describing what comes back and how to get the full article, and the optional-parameter behavior is stated. Minor gaps remain around empty results and how `locale` defaults interact with the user's language, but nothing blocks correct invocation.

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?

Schema coverage is 75%, so the schema carries most of the load, but the description adds one real semantic: `q` is optional and omitting it switches to listing all articles. It does not add anything about `category` or `locale` beyond what the schema already says, which keeps it from a 5.

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?

States a specific verb and resource ('Search SimianX's help center') and scopes the domain with concrete topics ('live analysis, deep analysis, autopilots, auto digest, points, plans, account'). It also distinguishes the browse mode from search and names the follow-up tool help_read, so an agent can place it among siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the user asks how something works on the website') plus a concrete exclusion-by-alternative: read the full article with help_read. It also covers the degenerate case ('Without `q` it lists the articles'), so both search and browse paths are routed.

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

All SimianX AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources