Skip to main content
Glama
platypus-db

platypus-db

Official

get_user_context

Request the user's active editor text, selection, or grid result from PlatypusDB to resolve vague on-screen references; sharing requires their explicit approval.

Instructions

Asks the user to share what they are looking at in the PlatypusDB app: the text of the active editor tab (editor), the part they selected (selection) and the result their grid shows (result: columns and rows). Use it when the user refers to something on their screen: "this query", "what I selected", "the result I see". Nothing is shared unless the user allows it in the app, each time or for your whole session; they can refuse, with a reason you get. parts limits what you ask for (all three by default). Answers connection, tab (its title) and the parts shared; the editor and selection are cut at 64 KiB, the result at 100 rows and 32 KiB (truncated says so). A tab on a connection that is not open to agents is not shared. Needs the app open; read-only: nothing runs.

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

Input Schema

NameRequiredDescriptionDefault
partsNoWhat to ask for: any of `editor`, `selection` and `result`; all three when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A3.5/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 disclosure burden, and it does that unusually well: it states the consent model (per-time or per-session, refusal with a reason), the requirement that the app be open, that closed-connection tabs are excluded, and that nothing runs (read-only). It also gives concrete truncation limits (64 KiB for editor/selection, 100 rows and 32 KiB for result) with a truncation flag. Only minor gaps remain, such as what a refusal response looks like structurally.

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-loaded with the purpose, followed by triggers, then permission and truncation behavior. The semicolon-chained clauses ('they can refuse, with a reason you get'; 'Needs the app open; read-only: nothing runs') are dense but each carries distinct 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 one-optional-param, no-output-schema tool this covers purpose, triggers, consent, prerequisites, connection restrictions, and truncation limits, which is close to everything an agent needs. Only the shape of the refusal response and whether parts order affects the answer are left implicit.

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?

With one optional parameter at 100% schema coverage, the schema already documents `parts` and its default. The description reinforces the default ('all three by default') and the enum members, adding no new meaning beyond the schema's own text, so the baseline 3 applies.

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?

States a specific verb and resource: it asks the user to share the active editor text, the selection, and/or the grid result from PlatypusDB. The three data parts are enumerated, so the tool is clearly distinguishable in kind from the DB-metadata siblings, though no sibling is named.

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?

Gives concrete trigger conditions with quoted user phrases ('this query', 'what I selected', 'the result I see') that map to the three parts. It does not exclude cases where a sibling (e.g. read_script, run_query) would be preferred, nor does it say what to do when the user refers to something not on their screen.

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