Skip to main content
Glama
Sign In
cardeck

cardeck

by shaonialife
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

logs_tail

Retrieve recent device log lines by device ID for remote CarDeck debugging; set line count up to 2,000 (default 200).

Instructions

取设备最近 N 行日志

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": {
      "deviceId": "<deviceId>"
    },
    "name": "logs_tail"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNo
deviceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it says nothing about permissions, whether the call blocks or streams, latency, or what happens for an offline device. '最近' hints at recency ordering, but that is the only behavioral signal.

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

Conciseness3/5

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

A single front-loaded sentence with no padding, but it is terse to the point of under-specification for a tool with two undocumented parameters. Efficiency is fine; the brevity costs information rather than saving it.

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

Completeness2/5

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

With no annotations, no output schema, and 0% schema description coverage, the description should explain the return shape (raw text vs. list of lines) and the tail semantics. Neither is present, so an agent cannot confidently predict the result.

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?

Schema description coverage is 0% and the description only gestures at both parameters ('设备' for deviceId, 'N 行' for lines). It omits that lines defaults to 200 and caps at 2000, and gives no hint about the expected deviceId format.

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 (取…日志) plus a scope qualifier (最近 N 行) tied to a device, so the agent knows it retrieves recent log output. It does not differentiate itself from sibling log tools logs_fetch and logs_file, leaving overlap unexplained.

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?

No guidance on when to prefer this over logs_fetch or logs_file, which are plausibly near-identical siblings. The only implicit cue is the 'recent N lines' framing, with no exclusions or prerequisites stated.

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