Skip to main content
Glama

Generate With Options

generate_with_options
Read-onlyIdempotent

Generate formatted placeholder text with headers, code blocks, and lists (HTML). Specify which elements to include: headers, code blocks, unordered lists, ordered lists.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": false,
      "count": 2,
      "length": "short",
      "headers": true,
      "ordered_lists": false,
      "unordered_lists": true
    },
    "name": "generate_with_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoInclude code blocks
countYesNumber of paragraphs to generate (1-10)
lengthYesLength of each paragraph
headersNoInclude random headers (h1-h6)
ordered_listsNoInclude ordered (numbered) lists
unordered_listsNoInclude unordered (bullet) lists

Output Schema

NameRequiredDescriptionDefault
htmlYesFormatted HTML output
countYesNumber of paragraphs requested
lengthYesLength of each paragraph
optionsYes
plain_textYesPlain text version with HTML tags stripped

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Number of paragraphs to generate (1–10)"New value: +"Number of paragraphs to generate (1-10)"
    • changedInput schema / properties / headers / description
      Previous value: -"Include random headers (h1–h6)"New value: +"Include random headers (h1-h6)"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Number of paragraphs requested",
      +      "type": "number"
      +    },
      +    "html": {
      +      "description": "Formatted HTML output",
      +      "type": "string"
      +    },
      +    "length": {
      +      "description": "Length of each paragraph",
      +      "enum": [
      +        "short",
      +        "medium",
      +        "long",
      +        "verylong"
      +      ],
      +      "type": "string"
      +    },
      +    "options": {
      +      "properties": {
      +        "code": {
      +          "description": "Include code blocks",
      +          "type": "boolean"
      +        },
      +        "headers": {
      +          "description": "Include random headers",
      +          "type": "boolean"
      +        },
      +        "ordered_lists": {
      +          "description": "Include ordered lists",
      +          "type": "boolean"
      +        },
      +        "unordered_lists": {
      +          "description": "Include unordered lists",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "headers",
      +        "code",
      +        "unordered_lists",
      +        "ordered_lists"
      +      ],
      +      "type": "object"
      +    },
      +    "plain_text": {
      +      "description": "Plain text version with HTML tags stripped",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "length",
      +    "options",
      +    "html",
      +    "plain_text"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "code": false,
      +    "count": 2,
      +    "headers": true,
      +    "length": "short",
      +    "ordered_lists": false,
      +    "unordered_lists": true
      +  },
      +  {
      +    "code": true,
      +    "count": 4,
      +    "headers": true,
      +    "length": "medium",
      +    "ordered_lists": true,
      +    "unordered_lists": true
      +  }
      +]
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds that output is HTML markup with headers, code blocks and lists, which is genuinely useful context beyond the annotations, but it says nothing about limits (e.g. count capped at 1-10), determinism of 'random headers', or the response shape.

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?

Two sentences, front-loaded with the core action and output format, with no filler. The second sentence's enumeration of element types partially duplicates the schema but reads as an efficient scoping hint rather than padding.

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 six-parameter generator with an output schema (so return values need no explanation) and annotations covering safety, the description is sufficient to call it correctly. The only real gap is that the paragraph-length and count controls, which govern the bulk of the output, go unmentioned in prose.

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%, so every parameter including count and length already carries its own description and the length enum is self-documenting. The description's element list largely restates the boolean property names, and it omits any mention of the required count and length parameters, so it adds no meaning beyond the schema.

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 concrete verb and resource ('Generate formatted placeholder text') and specifies the output format (HTML) plus the optional element types. It is clear what the tool produces, but it does not distinguish itself from sibling generators such as generate_paragraphs or generate_llms_txt, leaving the agent to guess which generator applies.

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?

'Specify which elements to include' is guidance on how to call it rather than when to call it, and no sibling alternative or exclusion is named. Usage is only implied: pick this when you need placeholder content with a chosen mix of structural elements, 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.