Skip to main content
Glama
Sign In

Presend MCP Server

by io.github.presendapp
OverviewDiscussionsAdmin

Password generator

password
Read-onlyIdempotent

Generates a random password, with options for length, symbols, uppercase, numbers and excluding ambiguous characters. To evaluate an existing password, use password_check.

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": "password"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoDesired password length. Defaults to a reasonable secure length if omitted.
numbersNoWhether to include numeric digits. 1 for yes, 0 for no.
symbolsNoWhether to include symbol characters. 1 for yes, 0 for no.
uppercaseNoWhether to include uppercase letters. 1 for yes, 0 for no.
exclude_ambiguousNoWhether to exclude visually ambiguous characters (e.g. 0/O, 1/l). 1 for yes, 0 for no.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / exclude_ambiguous / description
      Previous value: -""New value: +"Whether to exclude visually ambiguous characters (e.g. 0/O, 1/l). 1 for yes, 0 for no."
    • changedInput schema / properties / length / description
      Previous value: -""New value: +"Desired password length. Defaults to a reasonable secure length if omitted."
    • changedInput schema / properties / numbers / description
      Previous value: -""New value: +"Whether to include numeric digits. 1 for yes, 0 for no."
    • changedInput schema / properties / symbols / description
      Previous value: -""New value: +"Whether to include symbol characters. 1 for yes, 0 for no."
    • changedInput schema / properties / uppercase / description
      Previous value: -""New value: +"Whether to include uppercase letters. 1 for yes, 0 for no."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds only that output is random and that ambiguous characters can be excluded; it says nothing about output format, entropy guarantees, or whether defaults are safe. Adequate but thin beyond the annotations.

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?

Two sentences, no filler, with the core action front-loaded and the sibling routing placed second. Every clause earns its place.

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

Completeness4/5

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

For a zero-required-param generator with full schema coverage and no output schema, the description covers purpose, options, and the main alternative. It could note the default length or the return shape, but nothing critical is missing for correct invocation.

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 each parameter already documents its meaning and the 1/0 convention. The description's option list mirrors the schema without adding format or default details, so the baseline 3 applies.

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

Purpose5/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 password') and enumerates the configurable dimensions. It also explicitly distinguishes itself from the sibling password_check, so an agent can route between them without opening either schema.

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

Usage Guidelines4/5

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

Names the alternative tool and the condition that selects it ('To evaluate an existing password, use password_check'). It does not cover when not to use this tool or any prerequisites, but the primary routing decision is made explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Presend MCP Server toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources