SimianX AI

Search stocks and coins

search_instruments

Read-onlyIdempotent

Find the symbol to use: US stocks, ETFs and crypto pairs matching a name or ticker. To look up several names, pass them together in symbols (one call) instead of calling once per name.

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

Input Schema

Name	Required	Description
`q`	No	Name or ticker
`asset`	No	Default all
`limit`	No	Rows, up to 30 (default 10)
`symbols`	No	Up to 20 comma-separated names or tickers, answered in one call

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 13, 2026

addedInput schema / properties / symbols

Added value: +{
+  "description": "Up to 20 comma-separated names or tickers, answered in one call",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "q"
-]
```

First observedOct 16, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds the batch-efficiency behavior, which is useful, but says nothing about result ordering, ambiguous matches, or no-match behavior.

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?

Two sentences, purpose front-loaded, then the batching tip. No filler; only slight gain possible by stating what a result contains.

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?

Reasonable for a four-parameter, zero-required search tool with full schema coverage and annotations. It leaves out what a match returns and how misses are handled, and there is no output schema to compensate.

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 coverage is 100% with per-parameter descriptions, so 3 is the baseline. The description reinforces the semantics of symbols as a batch of names but adds no matching rules, format details, or asset-scope nuance beyond the schema.

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?

Specific verb and resource: 'Find the symbol to use' across US stocks, ETFs and crypto pairs matching a name or ticker. This clearly separates the resolution task from sibling tools that retrieve quotes, news or analysis.

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 clear operational guidance: use it to find the symbol, and batch multiple names via symbols in one call rather than one call per name. No explicit exclusions or named alternative tools, so it falls 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.

All SimianX AI tools Inspect

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.