Skip to main content
Glama
rubyLs

@rubyls/yearning-mcp

by rubyLs

列出数据源

yearning_list_sources
Read-onlyIdempotent

Filter and list data sources your account can access, selecting by query, DML, DDL, or IDC scope.

Instructions

列出当前账号有权限的数据源(可按 query/dml/ddl/idc 过滤)。对应 GET /api/v2/fetch/source

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tpNo数据源范围all
response_formatNomarkdown
Behavior3/5

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

注释已提供 readOnlyHint=true, idempotentHint=true, destructiveHint=false,安全行为已被覆盖。描述额外补充了权限范围过滤(query/dml/ddl/idc),提供了授权和筛选方面的有用上下文,但未涉及返回格式或分页等行为。

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?

描述仅一句话,以动词'列出'开头,包含核心功能、过滤能力及 API 端点,信息密度高且无冗余内容。

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?

工具本身简单且注释覆盖安全属性,但描述未说明 response_format 参数,也没有输出 schema,导致返回格式不明确;仅凭描述无法知晓如何请求 JSON 输出。整体上对于列表类工具已算基本完整,但仍有明显缺口。

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?

描述对 tp 参数进行了扩展('可按 query/dml/ddl/idc 过滤'),但未提及 response_format 参数。Schema 中 tp 描述为'数据源范围',response_format 无描述,整体 schema 描述覆盖率约 50%,描述未能弥补这一缺口。

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?

描述明确为'列出当前账号有权限的数据源',包含清晰动词、资源对象和权限范围。虽未显式对比 sibling 工具中的 list_databases/list_tables,但'数据源'这一概念足以区分主要用途,API 端点也增强了明确性。

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

Usage Guidelines3/5

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

描述隐含了使用场景(发现当前账号有权限的数据源),但未明确说明何时使用此工具而非 list_databases 或 list_tables,也没有提供任何排除条件或替代工具指引。

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rubyLs/yearning_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server