Skip to main content
Glama
This connector has been deprecated

Replaced by echopai-mcp.

Duplicate listing; superseded by io.github.echopai/echopai-mcp (official MCP Registry entry).

capabilities

Pass verb=<tool name> to get that tool's RESPONSE FIELD LIST locally — no request, no credits; do this before writing a projection instead of guessing field names. Without verb: the API spec_version — NOT this CLI's version, never infer one from the other — plus a newest-first changelog of capability changes; call at session start or when a response shape surprises you. Free, unauthenticated.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
verbNoTool / verb name (e.g. `scan`, `technicals`, `views`) or a raw cliKey (`quote.scan`). Returns its response field list from the bundled contract, locally: no request, no credits.
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
response_shapeNo按 views/news 的返回模式查询字段契约;须同时提供 verb
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses local execution, no request, no credits, free, and unauthenticated, and warns that the API spec_version is not the CLI version. It stops short of stating what happens for an unknown or invalid `verb` or how the field list is formatted.

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?

Both modes are front-loaded and each clause earns its place, with emphasis marking the highest-risk inference (spec_version vs CLI version). The em-dash-heavy phrasing and mid-sentence parentheticals make it denser than necessary, but nothing is wasted.

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?

For an eight-parameter, no-output-schema meta-tool, the description covers both modes, the cost/auth profile, and the recommended invocation timing. The remaining parameter details are fully documented in the schema, so nothing an agent needs to call it correctly is missing.

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 a baseline of 3 applies, but the description adds real meaning the schema does not: the default behavior when `verb` is omitted, and the framing of `verb` as either a tool name or raw cliKey. The `response_shape` coupling to `verb` is only in the schema, so it is not fully redundant.

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?

The description states a specific verb-plus-resource purpose and cleanly separates two modes: with `verb=<tool name>` it returns that tool's response field list locally, and without `verb` it returns the API `spec_version` plus a capability changelog. An agent can tell exactly what each invocation path produces without opening the 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?

It gives explicit when-to-use triggers ('do this before writing a projection instead of guessing field names', 'call at session start or when a response shape surprises you') and names the behavior it replaces — guessing field names. This is exactly the routing guidance a meta-tool needs, since the alternative is trial-and-error projection.

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