Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-litecoinAddress

Generates a random Litecoin address for mock payment data, testing, and placeholder wallet examples.

Instructions

Generates a random Litecoin address.

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": "finance-litecoinAddress"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/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 behavioral burden. It discloses only that output is 'random', without saying whether the address is syntactically valid, whether it corresponds to any real key, whether each call returns a different value, or that the output is fabricated test data — all material for a value that looks like a real financial identifier.

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 ten-word sentence with no filler and the key qualifier ('Litecoin') front and center. Nothing could be removed without losing information.

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

Completeness3/5

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

For a zero-parameter, zero-annotation generator with no output schema, the description covers what the tool does but not what the agent gets back or whether the result is safe to treat as real. Given that the output masquerades as a financial identifier, a note that the value is synthetic/for testing would close the main gap.

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 the baseline is 4; there is no parameter meaning for the description to add. The description correctly implies a parameterless call.

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 ('Generates') and resource ('random Litecoin address'), which distinguishes it from the sibling crypto generators finance-bitcoinAddress and finance-ethereumAddress by currency. It stops short of explicitly contrasting with those siblings, but the resource name alone makes selection unambiguous.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is given; usage is only implied by the fact that it is a zero-argument generator. An agent can reasonably infer this is for producing placeholder Litecoin addresses, but nothing in the text confirms that or rules out alternatives.

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