Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

database-type

Returns a random database column type for seeding schemas and test fixtures. Use it to populate mock tables with realistic column definitions.

Instructions

Returns a random database column type.

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-type"
  }
}

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 and no output schema means the description carries the full behavioral burden, and it discloses only that the result is random. It does not say what the value looks like (bare keywords like 'VARCHAR' vs. parameterized types like 'VARCHAR(255)'), what the pool of possible types is, or whether repeated calls can repeat values — the details an agent needs to consume the output safely.

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, hedging, or redundancy. Nothing could be removed without losing meaning.

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 trivial zero-input generator, the definition is nearly adequate, but with no output schema the description is the only place the return format and value domain could be stated, and it omits them. Adding one clause on the shape of the returned type string would make it complete.

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 input schema correctly has zero properties, so there are no parameters to explain and the description's silence on inputs is appropriate. Baseline 4 applies for a genuinely parameterless tool.

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 ('Returns a random database column type'), so an agent knows exactly what value it produces and can tell it apart from siblings like database-collation or database-column by the resource noun. It stops short of explicitly framing itself as part of a random-value generator family, which would have made the differentiation sharper.

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 guidance on when to use this versus the many other random-type generators (database-collation, database-engine, animal-type, etc.), nor any note that it takes no inputs and can be called freely. With a zero-parameter tool the usage question is simple, but the description still leaves the agent to infer that this is a pure random-value source rather than a lookup returning a fixed type.

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