Skip to main content
Glama
platypus-db

platypus-db

Official

list_scripts

Lists saved SQL scripts by project, showing path, folder status, and linked connection so agents can find available scripts before reading their contents.

Instructions

Lists the SQL scripts the user saved in PlatypusDB: path (relative to the project, with /), whether it is a folder, and the name of the connection a script opens on, if it is linked to one. project is the project's name as the app shows it; left out, the scripts of All connections. Scripts linked to a connection agents may not use are not listed. Read-only: use read_script for a script's text.

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

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's name, as the app shows it; left out for All connections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does so: it declares the operation read-only, describes the exact shape of each returned row, and discloses a non-obvious access filter ("Scripts linked to a connection agents may not use are not listed"). Remaining gaps are minor, such as ordering and whether the list is paginated.

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?

Front-loads what the tool returns, then the scoping rule, then the sibling pointer in a tight few sentences with no filler. The first sentence is long and comma-chained but still parseable, and every sentence carries information.

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 zero-required-parameter listing tool with no output schema, the description supplies return shape, scope default, access filtering, and the read-vs-text alternative. Only minor operational details (ordering, pagination via next_page) are unstated.

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%, and the single parameter's schema text ("The project's name, as the app shows it; left out for All connections") is nearly reproduced verbatim in the description. The description adds no meaning beyond the schema, so the baseline of 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 and resource ("Lists the SQL scripts the user saved in PlatypusDB") and enumerates the returned fields (path, folder flag, linked connection name). It also distinguishes itself from read_script, which returns script text, so an agent can pick the right tool without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to read_script when the script's text is needed, and explains the omission semantics of the project parameter ("left out, the scripts of All connections"). It does not enumerate other listing alternatives (e.g. list_connections), but the when-to-use context is clear.

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