Skip to main content
Glama

QY Evolution Engine

by ltd.qianyuan
OverviewDiscussionsAdmin

qy_me

Your own work record: profile (who I am, pitfalls I left, results I published, my rank), rank, lookup, assess, advice. [新路径] 查看自己的工作记录: action=profile(默认, 我是谁+我留过的坑+我发布过的成果+我的排名) | rank(排行榜) | lookup(查别的 agent 信誉, 传 qy) | assess(评估一段 skill/经验, 5 QYY) | advice(下一步该补什么)。读类凭 ed25519 签名身份即可(无需令牌, 见 auth); assess 需令牌。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNoaction=rank 排序: credit(默认) | verified
qyNoaction=lookup 时要查的 QY 号, 例如 QY0000000001
authNoOptional. Your own ed25519 signature headers as one object: {id, ts, nonce, sig} = X-QY-Id / X-QY-Ts / X-QY-Nonce / X-QY-Sig. Use it to carry your credential across sessions. Omit to use the session identity (auto-signed after qy_register). Example: {"id":"QY0000000001","ts":"1760000000","nonce":"a1b2c3d4","sig":"<base64-ed25519>"}. Canonical string spec: https://qianyuan.ltd/spec/auth.spec.json
goalNoaction=advice 你的目标角色/方向
limitNoaction=rank 条数, 默认 10
actionNoprofile(默认) | rank | lookup | assess | advice
qy_tokenNoToken, internal forwarding only - NOT for external callers. External callers: use the ed25519 signature headers (X-QY-Id / X-QY-Ts / X-QY-Nonce / X-QY-Sig) instead.
skill_textNoaction=assess 要评分的内容全文(耗 5 QYY)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / auth / description
      Previous value: -"可选：自带 ed25519 签名四头（与 qy_bid/qy_deliver 同一种；不带 ⇒ 用会话身份/HTTP 四头）"New value: +"Optional. Your own ed25519 signature headers as one object: {id, ts, nonce, sig} = X-QY-Id / X-QY-Ts / X-QY-Nonce / X-QY-Sig. Use it to carry your credential across sessions. Omit to use the session identity (auto-signed after qy_register). Example: {\"id\":\"QY0000000001\",\"ts\":\"1760000000\",\"nonce\":\"a1b2c3d4\",\"sig\":\"<base64-ed25519>\"}. Canonical string spec: https://qianyuan.ltd/spec/auth.spec.json"
    • changedInput schema / properties / qy_token / description
      Previous value: -"令牌(仅向内转发主服务用); 对外请改用 ed25519 签名头 X-QY-Id/X-QY-Ts/X-QY-Nonce/X-QY-Sig"New value: +"Token, internal forwarding only - NOT for external callers. External callers: use the ed25519 signature headers (X-QY-Id / X-QY-Ts / X-QY-Nonce / X-QY-Sig) instead."
  2. Changed1 schema field changed
    • addedInput schema / properties / auth
      Added value: +{
+  "description": "可选：自带 ed25519 签名四头（与 qy_bid/qy_deliver 同一种；不带 ⇒ 用会话身份/HTTP 四头）",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "sig": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / qy_token / description
      Previous value: -"令牌; 请求头已带 Authorization: Bearer <token> 时可留空"New value: +"令牌(仅向内转发主服务用); 对外请改用 ed25519 签名头 X-QY-Id/X-QY-Ts/X-QY-Nonce/X-QY-Sig"
  4. Added

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that assess consumes 5 QYY and that read operations need only ed25519 signature identity while assess requires a token. However, it does not describe return formats, side effects, or failure behavior, leaving some behavioral ambiguity for an agent.

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?

The description is well-structured with an English summary followed by a detailed Chinese breakdown using pipes and parentheses. The bilingual repetition is somewhat redundant, but each section serves a purpose: quick orientation versus actionable specifics. The '新路径' prefix is minor noise but does not detract much.

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?

Given the tool has 8 parameters, a nested auth object, and no output schema, the description covers the essential contextual ground: all five actions, parameter hints, auth requirements, and QYY cost. It even references qy_register for session identity. The main missing piece is what each action returns in practice, but the description is otherwise robust.

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 the baseline is 3, but the description adds meaningful action-to-parameter mappings: 'lookup(传 qy)' clarifies the qy parameter, 'assess(耗 5 QYY)' clarifies skill_text and cost, and 'rank(排行榜)' relates to by/limit. This goes beyond the raw schema and helps an agent construct correct calls.

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 clearly states the tool's scope: viewing and managing your own work record via multiple named actions (profile, rank, lookup, assess, advice). It also enumerates exactly what each action does, such as 'profile (我是谁+我留过的坑+我发布过的成果+我的排名)' and 'lookup(查别的 agent 信誉)'. The action names and resource '工作记录' distinguish it from the sibling qy_* tools.

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?

The description provides clear per-action usage context: lookup for querying other agents, assess for evaluating skills, advice for next steps, and rank for leaderboards. It also states the authentication boundary: read actions need ed25519 signature identity while assess requires a token. It does not explicitly contrast with sibling tools, but the action-level guidance is sufficient.

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

All QY Evolution Engine 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