Skip to main content
Glama
Sign In
Terminal Session Manager

Terminal Session Manager

by danieldoalto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Get Device

get_device

Look up a device's non-sensitive configuration using its nickname or ID to resolve connection details without exposing stored secrets.

Instructions

Retrieves non-sensitive device configuration by nickname or ID.

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": {
      "name_or_id": "<name_or_id>"
    },
    "name": "get_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
name_or_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that only non-sensitive configuration is returned, which is a real behavioral trait, but it omits auth requirements, error behavior for unknown devices, and side effects. A meaningful disclosure, but not comprehensive for an unannotated tool.

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?

A single tight sentence with the resource, qualifier, and identifier options front-loaded and zero filler. Every word earns its place.

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?

An output schema exists, so return values need no explanation, and the single required parameter is addressed. For a simple read tool the description is nearly sufficient; only failure behavior and sibling routing are absent.

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?

With one parameter and 0% schema description coverage, the description must compensate, and it partially does by clarifying that name_or_id accepts either a nickname or an ID. It does not state format, casing, or what happens on ambiguous matches, so the gap is only partly closed.

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 (retrieves) and resource (device configuration) with a qualifier (non-sensitive) that scopes what is returned. It implicitly distinguishes itself from list_devices and resolve_device by emphasizing single-device lookup by nickname or ID, though it does not name those siblings explicitly.

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 phrase 'by nickname or ID' hints at the retrieval context, but there is no explicit when-to-use guidance, no prerequisites, and no mention of when to prefer resolve_device or list_devices instead. The agent must infer routing from the name alone.

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