Skip to main content
Glama
platypus-db

platypus-db

Official

search_history

Retrieve past PlatypusDB SQL statements, newest first, and filter by connection, text, or origin to inspect how the user queries data.

Instructions

Searches the history of statements run in PlatypusDB, newest first, on the connections agents may use: connection, sql, started_at (UTC, RFC 3339), duration_ms, rows, status (ok, error or cancelled), error and origin (app for what the user ran, else the agent's name). connection limits it to one connection, text to statements containing it (ignoring case), origin to app or agent. 50 entries by default, up to 500 with limit. Use it to see how the user queries the data.

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

Input Schema

NameRequiredDescriptionDefault
textNoText the statement contains, ignoring case.
limitNoEntries returned at most: 50 by default, up to 500.
originNo`app` for statements the user ran, `agent` for those agents ran; both when left out.
connectionNoOnly this connection's statements: its name, as `list_connections` shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it enumerates the returned fields, spells out the status values (ok, error, cancelled), explains origin semantics (`app` vs agent name), and states the default and maximum page size. What it leaves vague is the permission boundary implied by 'connections agents may use' -- an agent cannot tell what happens if it targets a connection it lacks rights to.

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?

Purpose and ordering are front-loaded, and the field enumeration earns its place because no output schema exists. The middle sentence recapping connection/text/origin filters largely duplicates schema descriptions, which is the one clearly wasteful stretch.

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 four-parameter read tool with no output schema and no annotations, the description covers return fields, ordering, status vocabulary, pagination defaults and caps, and a use case -- enough to invoke it correctly. The remaining gap is the undefined visibility scope of 'connections agents may use'.

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 coverage is 100%, so the baseline is 3. The description restates filter semantics (connection narrows to one connection, text matches case-insensitively, origin takes app or agent, limit defaults to 50 and caps at 500) but adds essentially nothing beyond the schema's own property descriptions, and it omits the useful cross-reference that the schema gives to list_connections.

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?

Opens with a specific verb and resource -- searches the history of statements run in PlatypusDB -- and adds ordering (newest first) and scope (connections agents may use). It is unambiguous about what the tool returns, though it never names a sibling it is distinct from, even though top_queries and list_scripts could plausibly overlap.

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?

The closing sentence 'Use it to see how the user queries the data' gives one clear motivating scenario, which is more than most definitions offer. However, there are no exclusions or named alternatives, so an agent choosing between this and top_queries or list_open_sessions gets no routing help.

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