Skip to main content
Glama
platypus-db

platypus-db

Official

search_objects

Find objects in a database connection by matching text in names, columns, source, comments, notes, or #tags, ignoring case.

Instructions

Finds objects of a connection whose name contains a text, ignoring case; where the database supports it, also objects with such a column or in whose source the text appears; also objects whose comment or the user's notes contain it (matched comment or note), and #tag finds the objects the user tagged. At most 200 matches.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connection": "<connection>",
      "text": "<text>"
    },
    "name": "search_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText the object's name contains, ignoring case.
connectionYesThe connection's name, as `list_connections` shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A3.6/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 mostly succeeds: it discloses case-insensitive matching, database-dependent behaviors (column and source matching only "where the database supports it"), the #tag syntax, and a hard cap of 200 matches. Gaps remain around result ordering, whether the 200 limit means truncation that requires next_page, and error behavior for unknown connections.

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?

It is a single dense sentence, but the primary behavior (name contains text, case-insensitive) is front-loaded and the secondary matching modes fan out behind semicolons. Every clause conveys distinct behavior; only the length of the final sentence weighs against it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no annotations and no output schema, the description covers matching semantics and the match cap well. It does not describe the shape of returned objects or whether the 200 cap implies paging, which matters for an agent that may need to follow up.

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 both parameters are documented in the schema, establishing a baseline of 3. The description does add meaning beyond the schema by documenting the #tag convention for the text parameter and the extra fields that get matched, but it does not clarify the connection-name format beyond what the schema already says.

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 gives a specific verb and resource ("finds objects of a connection") and enumerates exactly which fields are searched: name, column name, source text, comment, user notes, and #tags. That is far more precise than a generic search tool. It stops short of naming a sibling such as list_objects, so the agent must infer the browse-vs-search split from names alone.

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 matching semantics: this is the tool for locating objects when you know some text associated with them. There is no explicit statement of when to prefer list_objects, or of exclusions such as using it for full-text SQL search. An agent can infer the intent but gets no routing guidance.

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