Skip to main content
Glama

Seedwall by seed (or today's)

seed
Read-onlyIdempotent

Generate a fixed generative-art image from a number between 1 and 999999, or omit the number to retrieve today's daily wallpaper for a surprise result.

Instructions

Every number from 1 to 999999 is one fixed Seedwall image, the same for everyone. Omit seed for today's daily wallpaper. Good for 'surprise me'.

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

Input Schema

NameRequiredDescriptionDefault
seedNoOmit for today's seed
widthNo
heightNo
previewNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description usefully adds determinism — the same seed always produces the same image for everyone — which is real behavioral context beyond the annotations, but it says nothing about output format (image URL vs binary), resolution behavior, or what preview actually does.

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?

Three short sentences with the key fact (deterministic 1-999999 mapping) front-loaded and the default behavior second; nothing is padded. The closing 'surprise me' aside is informal but earns its place as usage guidance.

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?

With four parameters, no output schema and thin schema coverage, the description should explain the rendering parameters and the return form. It covers only the seed/default case, leaving an agent unable to reason about width, height or preview from documentation alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: seed is documented, but width, height and preview have no description in either the schema or the description. The seed sentence largely restates the schema's own 'Omit for today's seed', and nothing explains whether preview returns a smaller/compressed image or how width/height interact with it, so the description fails to compensate for the coverage gap.

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 conveys the core resource and behavior: every integer 1-999999 maps to one fixed Seedwall image, identical for all users, and omitting the seed yields today's daily wallpaper. It is clear what the tool produces, though it never uses an explicit verb like 'return' or 'render' and does not distinguish itself from the render/describe_look siblings.

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?

It gives usable selection guidance ('Omit seed for today's daily wallpaper', 'Good for "surprise me"'), which tells an agent when the parameterless call is appropriate. It never names an alternative tool or a when-not-to-use condition, so routing among the siblings is left to inference.

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