Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-transactionDescription

Generates a random transaction description for mock finance data, enabling realistic test records for payment and accounting workflows.

Instructions

Generates a random transaction description.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It does reveal the key behavioral trait, non-deterministic random output, and that no inputs are required, but it never says what form the result takes (free-text string vs object), whether results repeat, or that it touches no real data. That leaves meaningful behavioral questions unanswered for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every word earns its place. It is minimal to the point that it omits useful detail, but nothing in it is redundant.

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?

This is a simple zero-parameter generator, so the bar is low, but with no output schema and no annotations the description should indicate the return value (a text description string) and confirm the data is fictitious. Without that, an agent knows the intent but not the shape of the result.

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 schema cannot be improved upon and there is nothing for the description to compensate for. 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.

Purpose4/5

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

The description states a specific verb and resource: it generates a random transaction description. An agent can tell this produces a synthetic description string rather than a type, amount, or account name. It does not explicitly contrast itself with nearby siblings such as finance-transactionType, but the resource is 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?

The word 'random' implies the tool is for synthetic/sample data rather than real transaction data, which is the only usage signal present. There is no explicit statement of when to prefer this over related generator tools, and no when-not guidance or prerequisites.

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