Skip to main content
Glama
JimmyAlter

guarded-sql-mcp

by JimmyAlter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get device

get_device
Read-onlyIdempotent

Retrieve details for a single device by its hostname, including its site and the assigned person's name and email.

Instructions

Get one device by hostname, including its site and the name and email of the person it is assigned to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostnameYesDevice hostname, e.g. "nb-lt-001". Case-insensitive.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
hasMoreYesMore rows matched than were returned.
rowCountYesRows in this response.
truncatedYesLong values were cut or rows dropped to fit the response size limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "hasMore": {
+      "description": "More rows matched than were returned.",
+      "type": "boolean"
+    },
+    "rowCount": {
+      "description": "Rows in this response.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "rows": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "assigned_email": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "assigned_to": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "hostname": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "ip": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "last_seen_at": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "os": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "site": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "site_name": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "description": "Long values were cut or rows dropped to fit the response size limit.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "rowCount",
+    "hasMore",
+    "truncated",
+    "rows"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar for additional disclosure is lower. The description adds return-content context (site and assigned person), but does not describe permissions, rate limits, not-found behavior, or other operational traits.

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 front-loaded sentence that states the action, scope, and returned details with no wasted words. It is appropriately sized for a simple read-only lookup tool.

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

Completeness5/5

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

Given the simple read-only operation, complete parameter schema, annotations, and the presence of an output schema, the description is sufficient. It summarizes the single-record lookup and its notable return fields without needing to duplicate the output schema.

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?

Schema description coverage is 100%, so the hostname parameter's pattern, length limit, example, and case-insensitivity are already documented in the schema. The description only repeats 'by hostname' and adds no syntax or format details beyond the schema.

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?

States a specific verb ('Get') and resource ('device') with singular scope ('one device by hostname'), which implicitly distinguishes it from search_devices and list-style siblings. It also names the returned entity context (site and assignee), so an agent knows this is a single-record lookup.

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 search_devices or other siblings, nor any exclusions. The only usage cue is the required hostname, which is already fully specified in the schema.

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