Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

system-filePath

Return a file path to populate mock datasets, test file operations, or fill placeholder file fields with realistic path values.

Instructions

Returns a file 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-filePath"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and delivers almost nothing. It doesn't disclose that the output is presumably a generated/synthetic value, whether it's deterministic, what platform path style it uses, or what a sample return looks like.

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?

One short sentence with no filler, but it is under-specified rather than concise – brevity here comes from omitting meaning, not from trimming waste. There is nothing front-loaded because there is no content to order.

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?

A zero-parameter, no-output-schema tool is simple, but the single critical fact – that it emits a synthetic file-path value, and in what form – is absent. An agent cannot confidently invoke or interpret this tool from the definition alone.

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 and the schema has additionalProperties: false, so there is nothing for the description to document. Baseline 4 applies since no parameter semantics are needed.

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 file path" restates the tool name system-filePath almost verbatim, adding no specificity. It hints at the file-vs-directory distinction relative to system-directoryPath, but never states the key fact an agent needs: whether this produces a real path, a randomly generated sample, or a template string.

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

Usage Guidelines1/5

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

No when-to-use, when-not-to-use, or alternative is mentioned. Nothing tells an agent whether to pick this over system-fileName, system-fileExt, or system-directoryPath, all of which are indistinguishable from this description alone.

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