Skip to main content
Glama
Sign In
tactus

tactus

by ProjectAILiberation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Scan for devices

scan_for_devices

Define a scan duration to discover new devices and receive a list of any additions found.

Instructions

Scan for new devices for a duration, then return any newly found.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scan_for_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
duration_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions scanning for a duration and returning new devices, but lacks details on blocking behavior, empty results, or state changes.

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?

One clear sentence with no fluff, front-loading the action and result.

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?

For a simple one-parameter tool without output schema, the description covers basic purpose and parameter usage, but lacks details on return format or behavior during scanning.

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 has 0% parameter description coverage. The description mentions 'for a duration' linking to duration_ms, but does not specify units, default, or behavior. Parameter name is self-explanatory but description adds minimal value.

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 scans for new devices over a duration and returns newly found ones. It distinguishes from sibling 'list_devices' which likely lists all known devices.

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

Usage Guidelines3/5

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

The description implies usage when wanting to discover new devices over time, but does not explicitly state when to use vs alternatives like 'list_devices' for current known devices.

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