Skip to main content
Glama
Agency MCP Server

Agency MCP Server

Structured data validation

validate_structured_data
Read-only

Extracts a page’s JSON-LD and validates LocalBusiness, Service, FAQPage, Article, and BreadcrumbList items for required and recommended properties and value shapes.

Instructions

Extracts the page's JSON-LD and checks LocalBusiness (and subtypes), Service, FAQPage, Article and BreadcrumbList items for required and recommended properties and value shapes.

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": {
      "client": "<client>",
      "url": "<url>"
    },
    "name": "validate_structured_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL inside the client's allowlist.
clientYesClient id from the server's config (dental, cafe, plumber).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing which schema types are in scope and that both 'required and recommended' properties plus 'value shapes' are checked — i.e., the checks are advisory-graded, not pass/fail only. It does not say whether the page is fetched live or from cache, nor whether it stops at the first error or reports all.

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?

A single sentence that front-loads the action ('Extracts the page's JSON-LD') before the scope list. No filler, no restatement of the name or title.

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?

With only two fully documented parameters and read-only annotations, an agent has what it needs to invoke correctly. The one remaining gap is that no output schema exists, so the description is the only place return shape could be described (e.g., per-item findings vs a flat issue list), and it is silent on that.

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%: 'url' is documented as an absolute URL inside the client's allowlist and 'client' as a config id with example values. The description adds nothing about either parameter, so the baseline 3 applies when the schema carries the burden.

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

Purpose4/5

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

States a specific verb sequence (extracts JSON-LD, then checks) and an enumerated scope of schema types (LocalBusiness and subtypes, Service, FAQPage, Article, BreadcrumbList) against required/recommended properties and value shapes. An agent reading this knows it is a structured-data validator, not a general page auditor. It does not explicitly contrast itself with the sibling audit_page, which keeps it below a 5.

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?

Usage is implied by the scope wording: use it to verify structured data markup on a page. There is no explicit when-to-use vs when-not, no mention of when audit_page would be the better call, and no stated prerequisite (e.g., page must be crawlable). Adequate but leaves routing to inference.

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