Skip to main content
Glama
JimmyAlter

guarded-sql-mcp

by JimmyAlter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find people

find_people
Read-onlyIdempotent

Search for people by partial name or email and return their name, email, department, and site for quick lookup.

Instructions

Find people whose name or email contains the given text. Returns name, email, department and site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum rows to return (1-100, default 25).
name_or_emailYesPart of a full name or email address. Matched literally: % and _ have no special meaning.

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": {
+          "department": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "email": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "full_name": {
+            "type": [
+              "string",
+              "number",
+              "boolean",
+              "null"
+            ]
+          },
+          "site": {
+            "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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the literal-match rule (also present in the schema) and lists return fields (covered by the output schema), so it contributes little genuinely new behavioral context, e.g. no case-sensitivity or empty-result behavior.

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?

Two short sentences, zero filler, with the core purpose and match rule front-loaded ahead of the return summary. Every clause 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?

For a simple read-only lookup with a full output schema and 100% parameter coverage, the description supplies everything needed to invoke it correctly. It is slightly redundant in restating return fields and omits minor details like case sensitivity, keeping it just short of fully 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?

Schema description coverage is 100%, so both parameters (name_or_email, limit) are already documented with pattern, length and default details. The description's 'contains the given text' merely restates the parameter without adding format or edge-case semantics beyond the schema. Baseline 3 applies.

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 (find) and resource (people) plus the exact matching semantics ('name or email contains the given text'), which is more than a restatement of the name. No sibling tool operates on people, so an agent can distinguish it immediately from list_sites, search_devices, and the other device-oriented siblings.

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?

Usage is implied by the name and the matching description, but there is no explicit when-to-use, no prerequisites, and no named alternative for related lookups. Adequate for a simple, single-purpose lookup tool, but it leaves the agent to infer context.

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