Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

system-directoryPath

Returns a placeholder filesystem directory path from the fake data generator. Use it to fill test data and templates with realistic path values without touching real disks.

Instructions

Returns a directory path.

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": "system-directoryPath"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, and it does not: it never says whether the path is synthetic/random or a real system path, whether it is absolute or relative, or what OS format to expect. The one useful nugget is that the call has no side effects and returns a string, but that is largely implied by the name and the empty schema.

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

Conciseness3/5

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

A single short, front-loaded sentence with no filler, but the brevity comes at the cost of under-specification rather than economy—nothing about format or typical output is conveyed.

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

Completeness2/5

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

The tool is simple (no params, no output schema), yet even for a trivial generator the description should state what the returned string looks like or that it is fabricated sample data. As written, an agent cannot predict the returned value's shape or platform conventions.

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 for the description to clarify beyond the schema. Baseline for a parameterless tool applies, with no gap to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns a directory path" essentially restates the tool name system-directoryPath and the title; it names a resource but offers no verb-level specificity beyond what the identifier already implies. It does not distinguish this generator from siblings such as system-filePath or system-commonFileName, which likely produce similar synthetic path-like strings.

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 the alternative path-related siblings, and no note on what the value is for (e.g., placeholder data in fixtures). The agent has to infer the use case entirely from the name.

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