Hopi

Schema markup generator

hopi_schema_markup_generator

Read-onlyIdempotent

Build valid JSON-LD structured data using schema.org. Supports FAQ pages, articles, local businesses and breadcrumb lists. Returns the JSON-LD object and a ready-to-paste script snippet. Source: https://hopi.co.uk/schema-markup-generator/

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	For type 'local': website URL
`faqs`	No	For type 'faq': questions and answers
`name`	No	For type 'local': business name
`town`	No	For type 'local': town or locality
`type`	Yes	The schema type to build
`hours`	No	For type 'local': opening hours
`items`	No	For type 'breadcrumb': ordered pages
`phone`	No	For type 'local': telephone
`author`	No	For type 'article': author name
`street`	No	For type 'local': street address
`headline`	No	For type 'article': the headline
`modified`	No	For type 'article': date modified
`postcode`	No	For type 'local': postal code
`published`	No	For type 'article': date published

Output Schema

TableJSON Schema

Name	Required	Description
`html`	No
`type`	No
`jsonLd`	No
`summary`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description is not burdened with safety disclosure. The description adds useful behavioral context by specifying that it returns both a JSON-LD object and a ready-to-paste script snippet, which goes beyond what the annotations state.

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?

The description is concise and front-loaded with the core purpose, followed by supported types and return behavior. The source URL at the end is somewhat auxiliary but does not seriously detract from the overall tight structure.

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 rich input schema with 100% parameter coverage, the conditional 'allOf' requirements, the existing output schema, and the annotations covering safety, the description provides everything needed for an agent to select and invoke the tool correctly. No critical information is missing.

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 the input schema already documents all 14 parameters with type-specific meanings. The description does not add parameter-level detail beyond the schema, which is acceptable given the complete 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 a specific verb ('Build') and resource ('valid JSON-LD structured data using schema.org'). It also lists the supported schema types (FAQ, article, local, breadcrumb) and the return format, making it easy to distinguish from generic generator siblings like hopi_meta_tag_generator.

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?

The description makes it clear that the tool is appropriate for generating schema.org JSON-LD for FAQ pages, articles, local businesses, and breadcrumbs. It does not explicitly state when not to use it or name alternatives, but the supported types provide clear context for selection.

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

All Hopi 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.

Resources

Need Help?