Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-emoji

Generates random emojis, optionally filtered by types like smiley, nature, or flag, to populate test data and sample content.

Instructions

Generates a random emoji.

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": "internet-emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoA list of the emoji types that should be included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.8/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, yet it says nothing about default behavior when types is omitted, whether the result is a single emoji or a list, or how sampling works. Only the word 'random' conveys any behavior.

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 sentence with no waste and the purpose front-loaded, but it is under-specified rather than genuinely economical. Brevity here comes at the cost of missing usage and return-value context.

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?

For a simple one-optional-param tool with no annotations and no output schema, the definition still omits what the tool returns and what the no-argument default is. Those are the two facts an agent most needs and neither appears in structured fields.

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% and the types parameter already enumerates its allowed values with a clear description, so the schema does the heavy lifting. The description adds nothing about the filter, which is the baseline case when coverage is high.

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?

States a specific verb and resource ('Generates a random emoji'), which is enough for an agent to tell this apart from the other internet-* generators by subject matter alone. It doesn't explicitly differentiate from siblings, but the resource noun does that implicitly.

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 optional category filter, and no statement about what happens when no types are supplied. The agent gets no help deciding between calling this bare versus filtered.

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