Skip to main content
Glama
Sign In
cardeck

cardeck

by shaonialife
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

notify

Displays custom alert text in a floating overlay on a specified CarDeck device, helping agents prompt users or signal issues during remote debugging.

Instructions

在设备悬浮窗上显示提示文字

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>",
      "text": "<text>"
    },
    "name": "notify"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
deviceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions the UI mechanism (floating window) but omits whether the device must be online, how long the notification persists, whether it is dismissible, and what the call returns.

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 a single front-loaded sentence with no filler. It is efficiently stated, though its brevity contributes to the specification gaps elsewhere.

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?

For a simple two-parameter tool with no annotations, no output schema, and zero schema description coverage, the description is too thin. It does not explain device targeting, required device state, display behavior, or return values.

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%, so the description must compensate. It only implies the 'text' parameter through '提示文字' and says nothing about 'deviceId', its format, or which device is targeted.

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?

The description states a specific action and resource: displaying prompt text in a device floating window. It is clear what the tool does, but it does not differentiate this from sibling tools such as prompt_reproduce or watch_stability.

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 description gives no explicit guidance on when to use this tool versus alternatives. There are no prerequisites, exclusions, or comparisons with sibling tools like prompt_reproduce or cmd.

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