Skip to main content
Glama
mcp-sql-gateway

mcp-sql-gateway

my_recent_queries

Access your own recent audit log entries to review queries and verify access.

Instructions

Show your own most recent entries in the audit log.

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": "my_recent_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses very little. It implies a read-only, self-scoped operation, but says nothing about how far back "recent" extends, the ordering of results, pagination, or any authorization requirement. For a tool with zero annotation coverage this is a notable gap, partly offset by the existence of an output schema that documents the return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no wasted words. It is appropriately sized for what it says, though its brevity is the cause of the transparency and parameter gaps rather than a virtue in itself.

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?

Treating this as a simple, single-parameter read tool whose output schema is already provided, the definition covers the essentials: what it returns and whose data it returns. The undefined notion of "recent" and the undocumented limit remain the only meaningful omissions.

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 description coverage is 0% and the single parameter (limit, default 10) is never mentioned in the description. The agent learns nothing about what the limit bounds, what the maximum is, or what happens when it is omitted, so the description does not compensate for the undocumented schema.

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?

The description pairs the verb "Show" with a specific resource and scope: "your own most recent entries in the audit log." That is enough to distinguish it from the sibling tools (describe_table, list_tables, run_query), though the mismatch between the tool name (my_recent_queries) and the description's framing (audit log entries) costs a point of sharpness.

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 only implied: "your own" signals a personal-scope read, so an agent knows it cannot use this to inspect other users' activity. There is no statement of when to prefer this over alternatives, no prerequisites, and no guidance on how the limit parameter should be chosen.

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