Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

database-engine

Returns a random DB engine to support mock data generation, testing, and prototyping.

Instructions

Returns a random database engine.

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": "database-engine"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the one key trait, randomness ('random' implies non-deterministic output on each call), but says nothing about whether the result is a plain string, its casing, or examples of possible values. For a zero-annotation tool that disclosure is thin.

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?

A single, front-loaded sentence with no filler and no redundancy. Every word (verb, randomness, resource) earns its place.

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?

With no output schema and no annotations, the description is the only source of truth, and it omits what a returned 'database engine' actually looks like (a name string such as 'PostgreSQL', a versioned identifier, etc.). For a trivial zero-param tool the gap is small but real.

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?

The tool takes zero parameters, so there is nothing in the schema for the description to explain; the baseline of 4 applies. The description does not introduce any phantom parameters or confuse the signature.

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: 'Returns a random database engine.' Combined with the tool name, an agent can tell this generates a single database-engine value, distinct from sibling generators like database-collation or database-column. It stops short of explicitly differentiating itself from the other database-* siblings, so not a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of seeding/mocking contexts, and no named alternative or exclusion. The intended use (generating a fake database engine for test data) is only inferable from the surrounding faker-style family, not from the definition itself.

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

Deploy Server

Other Tools