Skip to main content
Glama
Sign In

Crawlwise

by site.crawlwise
OverviewDiscussionsAdmin

Generate schema markup

generate_schema
Read-onlyIdempotent

Generate JSON-LD for a schema.org type from the fields you supply. Does NOT fetch the live page. Does NOT validate eligibility; use validate_schema for that.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "generate_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich schema to build. faq and howto earn no Google rich result.
fieldsNoThe values to fill in, such as name, url, headline, author, datePublished, price, priceCurrency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / fields / description
      Added value: +"The values to fill in, such as name, url, headline, author, datePublished, price, priceCurrency."
    • addedInput schema / properties / kind / description
      Added value: +"Which schema to build. faq and howto earn no Google rich result."
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "article",
+  "organization",
+  "local",
+  "product",
+  "person",
+  "breadcrumb",
+  "website",
+  "faq",
+  "howto"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by clarifying it operates purely on supplied fields rather than crawling, and that generated output is unvalidated. Minor gap: no note on what happens for missing required fields per kind.

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?

Three short sentences, zero waste: what it does first, then the two exclusions, then the redirect. Front-loaded and scannable.

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 2-parameter generator with a fully documented schema and no output schema, the description says enough to call it correctly and to know the result is JSON-LD that still needs validate_schema. It could go further on required fields per kind, but nothing essential 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%, including enum values and a note that faq/howto earn no rich result, so the schema carries parameter meaning. The description only echoes 'the fields you supply' and adds no format, required-field, or per-kind guidance beyond what the schema already states. Baseline 3 applies.

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?

States a specific verb and output ('Generate JSON-LD for a schema.org type from the fields you supply'), and immediately distinguishes itself from the closest sibling by naming validate_schema. An agent can pick between generate and validate without opening either schema.

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?

Explicitly routes the eligibility-checking use case to validate_schema and rules out live-page fetching ('Does NOT fetch the live page'), which is exactly the ambiguity an agent would hit for a schema-generation tool. Both when-to-use and when-not-to-use are stated.

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

All Crawlwise toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources