Skip to main content
Glama

Generate LocalBusiness schema

generate_schema
Read-onlyIdempotent

Generate LocalBusiness JSON-LD (schema.org) from business details and validate it against Google's rich result rules. Returns the JSON-LD, a ready-to-paste tag and issues to fix. No API key needed.

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": {
      "name": "<name>"
    },
    "name": "generate_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNo
urlNoWebsite URL (https://…)
logoNo
menuNo
nameYesPublic business name
emailNo
hasMapNo
imagesNo
ratingNoLocalSchema Pro — omitted from free output
sameAsNoGoogle Business Profile, Yelp, Facebook, LinkedIn… profile URLs
sloganNo
addressNo
reviewsNoLocalSchema Pro — omitted from free output
servicesNo
legalNameNo
telephoneNoInternational format, e.g. +31 50 123 4567
areaServedNo
priceRangeNoe.g. €€ or €20-€80
descriptionNo
businessTypeNoschema.org type, e.g. Dentist, Plumber, Restaurant. See /business-types.LocalBusiness
foundingDateNo
openingHoursNoRegular hours. Days not listed are closed. Use two entries for split hours.
specialHoursNoHoliday exceptions (LocalSchema Pro — omitted from free output)
alternateNameNo
knowsLanguageNo
servesCuisineNo
paymentAcceptedNo
serviceAreaOnlyNoTrue for service-area businesses without a storefront (address is hidden)
medicalSpecialtyNo
currenciesAcceptedNo
acceptsReservationsNo
isAcceptingNewPatientsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed36 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / address / additionalProperties
      Removed value: -false
    • removedInput schema / properties / geo / additionalProperties
      Removed value: -false
    • removedInput schema / properties / hasMap / $ref
      Removed value: -"#/properties/url"
    • addedInput schema / properties / hasMap / maxLength
      Added value: +2000
    • addedInput schema / properties / hasMap / type
      Added value: +"string"
    • removedInput schema / properties / images / items / $ref
      Removed value: -"#/properties/url"
    • addedInput schema / properties / images / items / maxLength
      Added value: +2000
    • addedInput schema / properties / images / items / type
      Added value: +"string"
    • removedInput schema / properties / logo / $ref
      Removed value: -"#/properties/url"
    • addedInput schema / properties / logo / maxLength
      Added value: +2000
    • addedInput schema / properties / logo / type
      Added value: +"string"
    • removedInput schema / properties / menu / $ref
      Removed value: -"#/properties/url"
    • addedInput schema / properties / menu / maxLength
      Added value: +2000
    • addedInput schema / properties / menu / type
      Added value: +"string"
    • removedInput schema / properties / openingHours / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / openingHours / items / properties / closes / $ref
      Removed value: -"#/properties/openingHours/items/properties/opens"
    • addedInput schema / properties / openingHours / items / properties / closes / pattern
      Added value: +"^([01]\\d|2[0-3]):[0-5]\\d$"
    • addedInput schema / properties / openingHours / items / properties / closes / type
      Added value: +"string"
    • removedInput schema / properties / rating / additionalProperties
      Removed value: -false
    • addedInput schema / properties / rating / properties / reviewCount / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / reviews / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / sameAs / items / $ref
      Removed value: -"#/properties/url"
    • addedInput schema / properties / sameAs / items / maxLength
      Added value: +2000
    • addedInput schema / properties / sameAs / items / type
      Added value: +"string"
    • removedInput schema / properties / services / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / services / items / properties / url / $ref
      Removed value: -"#/properties/url"
    • addedInput schema / properties / services / items / properties / url / maxLength
      Added value: +2000
    • addedInput schema / properties / services / items / properties / url / type
      Added value: +"string"
    • removedInput schema / properties / specialHours / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / specialHours / items / properties / closes / $ref
      Removed value: -"#/properties/openingHours/items/properties/opens"
    • addedInput schema / properties / specialHours / items / properties / closes / pattern
      Added value: +"^([01]\\d|2[0-3]):[0-5]\\d$"
    • addedInput schema / properties / specialHours / items / properties / closes / type
      Added value: +"string"
    • removedInput schema / properties / specialHours / items / properties / opens / $ref
      Removed value: -"#/properties/openingHours/items/properties/opens"
    • addedInput schema / properties / specialHours / items / properties / opens / pattern
      Added value: +"^([01]\\d|2[0-3]):[0-5]\\d$"
    • addedInput schema / properties / specialHours / items / properties / opens / type
      Added value: +"string"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, and the description does not contradict them. It adds useful behavioral context: validation against Google's rich result rules, returned JSON-LD, a script tag, issues to fix, and no API key requirement. It does not disclose free-output omissions or rate limits, but the main behavioral profile is clear.

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 three compact sentences, front-loads the core action and validation scope, and includes only useful supporting details such as return values and no API key needed. There is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's output shape reasonably well despite there being no output schema, and annotations cover safety properties. However, for a 32-parameter nested input tool, it is incomplete about parameter expectations, required-only-name behavior, free-output omissions, and sibling alternatives.

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?

There are 32 parameters with only 34% schema description coverage, and the description provides no parameter-level semantics beyond 'business details'. It does not explain required vs optional fields, nested structures, or the schema's free-output limitations, so it fails to compensate for the low schema coverage.

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?

The description gives a specific verb and resource: generate LocalBusiness JSON-LD from business details and validate it against Google rich result rules. It clearly distinguishes generation-plus-validation from pure validation siblings, though it does not explicitly name alternatives such as validate_schema or get_embed_snippet.

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 'from business details' and the generation/validation framing, but the description gives no explicit when-to-use, when-not-to-use, or alternatives. An agent can infer this is for creating new LocalBusiness schema, but sibling routing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources