Skip to main content
Glama
agentrix-ai

Uno MCP Stdio

by agentrix-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

uno_search_tools

Search MCP tools by keyword, category, or natural language, then retrieve matching tool definitions and parameters ready for invocation.

Instructions

搜索 MCP 工具。直接返回最相关的 tools 及完整参数定义，可立即调用 uno_call_tool。

【可用资源】共 144 个 MCP Server，使用 query 搜索。

【用法】

  1. 关键词搜索：uno_search_tools(query="天气")

  2. 语义搜索：uno_search_tools(query="帮我查北京天气", mode="hybrid")

  3. 分类浏览：uno_search_tools(category="金融")

【返回内容】

  • tools: 最相关的工具列表，每个包含 tool、desc、inputSchema，以及统计（rating/avg_ms/calls_7d/success_rate）

  • uncached: 需要先认证的 OAuth server（如有），调用 uno_connect_server 触发认证

  • 统计字段帮你选择更可靠的工具：calls_7d 高 = 热门，rating 高 = 好评，avg_ms 低 = 快

【工作流】 uno_search_tools(query="天气") → 拿到 tools → 立即 uno_call_tool(tool_name="amap-maps.maps_weather", ...)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo搜索模式: keyword(精确,快) / semantic(语义理解) / hybrid(混合,推荐)
limitNo返回 tool 数量，默认 5，最大 15
queryYes搜索关键词（中英文均可），支持自然语言
categoryNo按分类浏览，如 '搜索', '开发', '金融', '社交'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does well: it discloses that results include inputSchema, that some servers are OAuth-gated ('uncached', requiring uno_connect_server), and it explains the meaning of the statistics fields (calls_7d/rating/avg_ms). It stops short of covering error behavior, rate limits, or latency caveats, so it is strong but not exhaustive.

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?

Front-loaded with purpose, then uses bracketed sections (可用资源/用法/返回内容/工作流) that make it skimmable and scannable. Slightly verbose with repeated tool-name spellings in the examples, but every section earns its place.

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

Completeness5/5

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

No output schema exists, yet the description fully describes the return shape (tools with tool/desc/inputSchema, uncached OAuth list, statistics), the auth follow-up path, and the end-to-end workflow. For a discovery/routing tool this is complete enough to call correctly on the first try.

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 100%, so baseline is 3, but the description adds real value beyond the schema by showing worked examples of query semantics (natural-language queries), the practical difference between mode values, and category strings. It does not elaborate on limit beyond what the schema already says.

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?

Opens with a precise verb+resource ('搜索 MCP 工具' / search MCP tools) and immediately states the scope (144 MCP servers) plus what is returned ('最相关的 tools 及完整参数定义'). An agent can distinguish this from search-oriented siblings like uno_skills_search because the domain (MCP tools vs skills) and the immediate-callability of results are named.

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?

Provides three explicit invocation patterns with concrete argument examples (keyword, semantic/hybrid, category browse) and a named end-to-end workflow ending in uno_call_tool. The mode distinction ('keyword 精确/快' vs 'semantic 语义理解' vs 'hybrid 推荐') tells the agent exactly which mode to pick for which query shape.

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

Deploy Server

Other Tools