Skip to main content
Glama
dinosaur24

mockhero

by dinosaur24
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

list_templates

Discover pre-built database schema templates for common application patterns like ecommerce, blogs, SaaS platforms, and social networks to accelerate test data generation.

Instructions

List pre-built schema templates for common application patterns.

Available templates:

  • ecommerce: Customers, products, orders, order items, reviews (5 tables)

  • blog: Authors, posts, comments, tags, post_tags (5 tables)

  • saas: Organizations, members, subscriptions, invoices (4 tables)

  • social: Users, posts, likes, follows, messages (5 tables)

Each template includes realistic field types, proper foreign key relationships, weighted enum distributions, and auto-locale detection via country fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • packages/mcp/src/tools.ts:296-298 (handler)
    The handler function for the 'list_templates' tool which calls the underlying template listing function.
    function handleListTemplates(): ToolResult {
  return ok(listTemplates());
}
  • src/lib/engine/templates/index.ts:25-34 (helper)
    The actual implementation that returns a list of template summaries from the template registry.
    export function listTemplates(): TemplateSummary[] {
  return Object.values(TEMPLATE_REGISTRY).map(
    ({ id, name, description, tables, default_counts }) => ({
      id,
      name,
      description,
      tables,
      default_counts,
    }),
  );
  • packages/mcp/src/tools.ts:368-370 (registration)
    The registration logic within the main tool switcher in packages/mcp/src/tools.ts.
    case "list_templates":
  return handleListTemplates();
case "generate_from_template":

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by detailing what the tool returns (specific templates with their table structures and features like foreign keys, enum distributions, and locale detection). It doesn't mention rate limits, authentication needs, or pagination, but provides substantial behavioral context for a read-only listing operation.

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?

The description is front-loaded with the core purpose, followed by a bulleted list of templates and additional features. Every sentence adds value: the first states the action, the bullets provide concrete examples, and the last explains template characteristics. No wasted words.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is nearly complete. It explains what templates are available and their features, but doesn't specify the return format (e.g., JSON structure) or any error conditions, leaving a minor gap for agent invocation.

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 has 0 parameters with 100% schema coverage, so the baseline is 4. The description adds no parameter information (as there are none), which is appropriate and doesn't detract from the high schema coverage.

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 clearly states the tool's purpose with specific verb ('List') and resource ('pre-built schema templates for common application patterns'). It distinguishes from siblings like 'detect_schema' (which analyzes existing schemas) and 'generate_from_template' (which creates from templates) by focusing solely on listing available templates.

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 description implies usage by providing template details, but doesn't explicitly state when to use this tool versus alternatives like 'generate_from_template' or 'list_field_types'. It suggests context for selecting templates but lacks explicit guidance on prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dinosaur24/mockhero'

If you have feedback or need assistance with the MCP directory API, please join our Discord server