Skip to main content
Glama

tmpstate

by dev.tmpstate

Create a temporary database

create_database

Create a temporary JSON database (24h TTL, no signup, no keys). Returns the db URL — the only credential — plus admin URL, limits and expiry. Create once per project/task, persist the db URL immediately (local ~/.tmpstate/credentials, project README, and your memory), and reuse it instead of creating again. For retries or parallel workers, pass a stable idempotency_key so duplicate calls return the same database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idempotency_keyNoStable retry key. Reusing it from the same client returns the same database.

TDQS

A4.7/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses TTL (24h), no signup/keys, return values (db URL, admin URL, limits, expiry), and idempotency behavior. Fully transparent about what the tool does and its constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with core functionality, followed by usage guidance. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Given the simple tool (1 param, no output schema, no annotations), the description covers creation behavior, TTL, returned data, usage pattern, and retry semantics. Fully complete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a schema description. Description adds meaning by explaining the purpose of idempotency_key for retries and parallel workers, going beyond the schema's brief description.

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?

Clearly states 'Create a temporary JSON database', specifying the resource (temporary JSON database) and the action (create). Distinguishes from sibling tools like pro_create_database by emphasizing no signup, no keys, and 24h TTL.

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?

Explicit instructions: 'Create once per project/task... reuse it instead of creating again' and for retries using idempotency_key. Provides clear context but lacks explicit when-not-to-use alternatives.

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

All tmpstate toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Resources