designforyou

by org.swapp1990.designforyou

Recommend a template

recommend_template

Read-only

Recommend the best matching templates for any use case. Describe what you need and the system auto-detects the category and ranks templates by relevance. Return the recommendations so the user can pick a template from the visual gallery; do not call generate in the same turn unless the user explicitly names a template_id or asks you to skip selection.

Input Schema

TableJSON Schema

Name	Required	Description
`needs`	No	Optional explicit needs such as favicon, navbar, og-image
`category`	No	Optional category override. Auto-detected from use_case if not provided.
`use_case`	Yes	Describe what you need the template for (e.g. 'Instagram post for a restaurant daily special', 'logo for a fitness brand')
`subcategory`	No	Optional subcategory constraint such as lettermark or app_icon

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJun 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses key behaviors: auto-detecting category, ranking by relevance, returning recommendations for user selection, and the exact condition to call generate. This adds meaningful context not present in 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, front-loaded with the main verb and resource, and every clause serves a purpose: purpose, workflow, and explicit guardrail. No fluff or redundancy.

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

Completeness5/5

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

Given the output schema and complete parameter descriptions, the description fully covers the tool's purpose, usage flow, and key constraints. It is sufficient for the agent to select and invoke correctly without additional context.

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?

The input schema already covers all parameters with descriptions (100% coverage), including auto-detection for category. The description adds only a general 'Describe what you need' which overlaps with the use_case parameter. Minimal added semantic value beyond schema.

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?

The description opens with a specific verb and resource: 'Recommend the best matching templates for any use case.' It clearly distinguishes from siblings like browse_templates (generic browsing) and generate (template generation) by focusing on auto-detection and relevance ranking.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance ('any use case') and an explicit exclusion: 'do not call generate in the same turn unless the user explicitly names a template_id or asks you to skip selection.' This is concrete, actionable direction for the agent.

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

All designforyou tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.