Skip to main content
Glama

Plan structured data

schema.plan

Generates JSON-LD structured data plans for Organization, WebSite, and BlogPosting pages from a website repository root.

Instructions

Specialized: Organization/WebSite/BlogPosting JSON-LD plans. No sitewide FAQ schema.

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": {
      "projectRoot": "<projectRoot>"
    },
    "name": "schema.plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
projectRootYesAbsolute path to the website repository root
includeBlogPostingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: not whether the tool writes files into projectRoot or only returns a plan object, whether it requires credentials, or what the result looks like. The single useful behavioral fact is the exclusion of sitewide FAQ schema, which is a scope constraint rather than an operational trait.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments, front-loaded with the specialization, so there is no wasted wording. However, the terseness crosses into under-specification — the sentence fragments read like internal shorthand rather than a self-contained definition.

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 no annotations, no output schema, and two of three parameters undocumented, the description would need to carry most of the context, and it delivers only a type list plus one exclusion. An agent cannot tell from this definition what it receives back or how the boolean parameter alters the plan.

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 33% (only projectRoot is documented in the schema), and the description adds no parameter meaning at all — siteUrl and includeBlogPosting are never mentioned. With low coverage the description was expected to compensate, and it does not, so the agent must guess whether siteUrl is required for correct URL resolution or what disabling includeBlogPosting changes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource concretely (Organization/WebSite/BlogPosting JSON-LD) and implicitly the verb via the tool name 'plan', but 'plans' is used as a bare noun with no verb phrase, so an agent must infer that the tool produces a plan rather than analyzing or validating one. The type enumeration does help distinguish it from generic SEO tools, but the scope of the output (per-page vs sitewide) is only hinted at by the FAQ exclusion.

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

Usage Guidelines2/5

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

The only guidance is a negative exclusion ('No sitewide FAQ schema'); there is no positive statement of when to call this tool and no named alternative for the excluded case. Siblings such as seo.plan_changes or content.brief are never referenced, so the agent has no routing signal beyond the exclusion itself.

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