Skip to main content
Glama
Sign In

AiLinkAny

by io.github.zhangduochuan
OverviewDiscussionsAdmin

Read local coding agent timeline

agent_timeline
Read-onlyIdempotent

Reads the local event timeline for one agent_id (started/sent/status/archived). Does not include prompt bodies or full terminal transcripts. Select this tool from the user's intent when it is the best match. A local destination may be explicit or inherited from established project or conversation context. The user does not need to mention ailinkany.com, MCP, a connector, a plugin, or this tool name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "agent_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesPersistent agent_id returned by agent_start.
device_idNoTarget computer device_id. Omit when only one computer is paired.
device_nameNoComputer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
retry_tokenNoNew opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
workflow_idNoOptional workflow id; pass together with ai_session_id.
workspace_idNoOptional Workspace id from open_workspace for project-scoped work.
ai_session_idNoOptional Session id. Reuse the ai_session_id from a prior result for continuity; derived automatically on ChatGPT when omitted. Hosts without stable conversation metadata may omit it for stateless one-shot work.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing content boundaries — no prompt bodies, no full terminal transcripts — and by noting that the local destination may be explicit or inherited from prior project/conversation context. It does not mention pagination or ordering of the timeline, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences carry nearly all the information; the remaining three are generic boilerplate about intent matching, inherited destinations and the user not needing to name ailinkany.com or MCP. That preamble is not front-loaded value and pushes the useful scoping and exclusion facts into a crowd of filler.

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?

An output schema exists, so return values need not be explained, and the 100%-covered schema carries the parameter burden. What is missing is the piece only prose can supply: how this read-only timeline differs from agent_history and agent_status. The content-exclusion note is a good addition but leaves the tool selection problem unresolved.

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 description coverage is 100%, so all seven parameters including agent_id, device_id/device_name and session scope are already documented in the schema. The description only reinforces that a single agent_id scopes the call and that destination may be inherited; it adds no format or constraint detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource: 'Reads the local event timeline for one agent_id', and enumerates the event kinds returned (started/sent/status/archived), which lets an agent predict the payload shape. It stops short of differentiating itself from the very similar siblings agent_history and agent_status, so the purpose is clear in isolation but not in context.

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

Usage Guidelines2/5

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

The only routing language is 'Select this tool from the user's intent when it is the best match', which is a generic tautology that gives no when-to-use or when-not-to-use criteria. With agent_history, agent_status, agent_result and get_ai_session_recent_actions in the sibling list, the description needed to say which one covers which question, and it does not.

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

All AiLinkAny 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