Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

system-fileExt

Returns a file extension from a provided MIME type, helping you correctly identify file formats for processing or display.

Instructions

Returns a file extension.

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

Input Schema

NameRequiredDescriptionDefault
mimeTypeNoValid mime-type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and largely fails it. It does not say what the returned extension looks like (leading dot or not), what happens for an unrecognized MIME type, or whether the lookup is a pure read with no side effects.

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?

The description is a single short sentence with no wasted words, which is good. The problem is under-specification rather than verbosity: the available space is not used to convey anything an agent could act on.

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?

Although the tool is simple (one optional parameter, no output schema, no nesting), the description leaves out the input domain and the output format. An agent cannot tell what the returned string looks like or how failure cases are signalled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with a single well-labelled mimeType parameter, so the baseline of 3 applies. The description adds nothing beyond the schema, but nothing critical is missing from the structured field either.

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

Purpose3/5

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

"Returns a file extension" gives a verb and a resource, so the basic operation is understandable. However, it never says the input is a MIME type and never distinguishes this tool from near-identical siblings such as system-commonFileExt or system-fileType, leaving the agent to guess which one to call.

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 statement of prerequisites, and no mention of alternatives. With several sibling tools covering file extensions, names, paths, and types, the agent has no signal for choosing this one over the others.

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