Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

database-mongodbObjectId

Generates a MongoDB ObjectId string for use as a unique database identifier.

Instructions

Returns a MongoDB ObjectId string.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it only discloses the return type, not whether values are random or deterministic, unique per call, or formatted as 24 hex characters. For a trivial zero-argument generator the bar is low, so this is minimum viable rather than deficient.

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 short sentence with zero filler, front-loading the only fact that matters. Nothing is repeated from the name in a wasteful way.

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 generator this is close to complete, but with no output schema the description should state the actual shape of the returned string, such as a 24-character hexadecimal identifier. As written, an agent knows the type but not the format or uniqueness guarantees.

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 no parameters, so there is no parameter semantics to explain; the baseline for a zero-parameter tool applies. The description correctly implies no inputs are needed.

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 states a concrete verb and resource: it returns a MongoDB ObjectId string. That is unambiguous and distinguishes it from siblings like database-collation or database-type. It does not explicitly contrast itself with any alternative, which keeps it just below 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 Guidelines3/5

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

Usage is only implied: it is a zero-parameter generator, so an agent can reasonably infer it should be called when a MongoDB-style ObjectId value is needed. There is no explicit when-to-use or when-not-to-use statement, and no mention of alternatives.

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