Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

science-chemicalElement

Returns a random periodic table element for testing, demos, or generating sample chemistry data.

Instructions

Returns a random periodic table element.

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": "science-chemicalElement"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and delivers little beyond the word "random", which at least signals non-determinism. It says nothing about whether repeated calls can repeat a value, whether seeding or reproducibility exists, or what the returned element representation looks like — significant gaps for a tool whose entire output is the behavior.

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 front-loaded sentence with no filler, restatement, or hedging. Nothing in it is wasted, and the key information (random + periodic table element) arrives first.

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?

There is no output schema and no annotations, so the description is the only source of truth about the return value, and it never specifies the shape (string name, symbol, atomic number, or object). For a zero-argument tool whose whole contract is its output, that leaves the definition materially incomplete.

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 no parameter meaning for the description to add; the baseline of 4 applies. The empty schema is consistent with the description's implication that no input is required.

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 gives a specific verb and resource ("Returns a random periodic table element"), so an agent immediately knows it produces a chemical element. It stops short of distinguishing itself from the sibling science-unit tool or clarifying whether the element comes back as a name, symbol, or structured object.

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 or when-not-to-use guidance, no mention of alternatives such as science-unit, and no indication of the scenario this suits (seeding test data, sampling, display). The only implied usage is the bare semantics of "random", which the agent must infer.

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