Skip to main content
Glama
ThinAirTelematics

ThinAir Data

Official
by ThinAirTelematics
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

show_locks

List active database sessions and identify blocking locks using system views for PostgreSQL, MySQL, and SQL Server.

Instructions

List active sessions + blocking locks. Uses the dialect's own system view: pg_stat_activity on postgres, information_schema.processlist on mysql, sys.dm_exec_requests joined with sys.dm_tran_locks on mssql. [BUILD tier]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • bin/server.js:131-136 (registration)
    The 'show_locks' tool is registered in the TOOLS catalog array. However, this is a static reference adapter — it does not implement tool execution locally. The actual handler for 'show_locks' lives on the hosted backend at https://data.thinair.co/mcp. This local server only returns a redirect message for all tool calls.
    {
  name: "show_locks",
  description:
    "List active sessions + blocking locks. Uses the dialect's own system view: `pg_stat_activity` on postgres, `information_schema.processlist` on mysql, `sys.dm_exec_requests` joined with `sys.dm_tran_locks` on mssql. [BUILD tier]",
  inputSchema: { type: "object" },
},

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses underlying system views per dialect, which is useful behavioral context. However, it does not mention whether the operation is read-only or if it requires special permissions.

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 sentences efficiently convey the tool's purpose and implementation details without unnecessary words. Front-loaded with the core action.

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 tool with zero parameters and no output schema, the description is fairly complete: it explains the action and the underlying system views. Could be enhanced by noting dialect support or expected output, but overall sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema is an empty object, so no parameters to document. Description does not explain the return value, but with zero parameters, the baseline is 4. No additional meaning is needed beyond what the schema provides.

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?

Clearly states it lists active sessions and blocking locks, specifying dialect-specific system views. Distinguishes from sibling tools as it is the only one focused on locks and sessions.

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?

Does not provide explicit guidance on when to use or not use this tool versus alternatives. The description implies usage for lock monitoring but lacks context on alternatives like 'analyze_table' or 'explain_query'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ThinAirTelematics/thinair-data'

If you have feedback or need assistance with the MCP directory API, please join our Discord server