Skip to main content
Glama
Sign In
DG-MCP

DG-MCP

by 0xNullAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

connect

Establish a Bluetooth connection to a Coyote device. Provide the BLE address obtained from scanning.

Instructions

连接到指定的 Coyote 设备。需先调用 scan 获取地址。

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": {
      "address": "<address>"
    },
    "name": "connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesBLE 地址（aa:bb:cc:dd:ee:ff）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral details such as whether the connection is blocking, idempotent, or what happens on success/failure. For a connection tool, more transparency on side effects or state changes is needed.

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

Conciseness5/5

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

The description consists of two concise sentences with no redundant information. It front-loads the action and prerequisite efficiently.

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's simplicity (one required parameter, no output schema), the description covers the essential context: what to do and what is needed beforehand. It lacks details about return behavior or errors, but overall it is mostly complete.

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?

The schema already provides 100% coverage for the single parameter, describing it as a BLE address. The description adds no further meaning beyond restating the requirement, meeting the baseline but not exceeding it.

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 clearly states the tool connects to a Coyote device, using a specific verb and resource. However, it does not differentiate from sibling tools like 'scan' or 'disconnect' beyond indicating a prerequisite.

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 explicitly states the prerequisite to call 'scan' first to obtain the address, providing clear when-to-use guidance. This helps the agent avoid misuse.

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