pro_list_databasesList the Pro account's databases (ids, usage, limits, expiry) so a fresh session can reconcile against persisted db URLs. URLs are never stored server-side — match ids to the URLs you persisted.
| Name | Required | Description | Default |
|---|---|---|---|
| pro_token | No | Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_... |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It notes that URLs are never stored server-side, which is useful. However, it does not disclose whether the tool is read-only, requires authentication details beyond the token, or has rate limits or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, each serving a distinct purpose: the first states the main function and return data, the second adds an important behavioral note. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description mentions what is returned (ids, usage, limits, expiry) and the use case, but without an output schema, it does not specify the output format, pagination, or error handling. It is adequate for a simple list tool but could be more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage with a single parameter pro_token. The description adds practical context: the token format (pt_...) and that it is optional if the MCP connection already sends Authorization header. This goes beyond the schema description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (list), the resource (Pro account's databases), and what data is returned (ids, usage, limits, expiry). It also explains the use case (reconcile against persisted URLs). This distinguishes it from other database-related sibling tools like create_database or list_documents.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use (fresh session reconciliation) but does not explicitly state when not to use or suggest alternatives among the many sibling tools. It lacks guidance on choosing between this and tools like database_status or pro_create_database.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, with descriptions that differentiate similar operations (e.g., create_database vs pro_create_database vs pro_attach_database). Agents can easily select the correct tool.
Most tools follow a verb_noun snake_case pattern, but 'database_status' is noun_verb. The 'pro_' prefix is consistently used for Pro account tools. Overall pattern is clear and predictable.
16 tools cover the full lifecycle of temporary databases, document CRUD, collection management, and Pro account operations. Each tool is justified and the count feels well-scoped for the domain.
The tool surface provides complete CRUD for documents, database lifecycle (create, delete, extend, status), and full Pro account management (checkout, cancel, create, attach, list). No obvious gaps for the stated purpose.