Skip to main content
Glama

ADS Beast

seo_schema_generate

Schema.org JSON-LD for a page (FAQ, HowTo, Article, Product, LocalBusiness, Organization), stored as a suggestion. AI: 1 AI request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo_schema_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNohttps:// page URL.
contentNoWhat the page contains.
client_idNo
brand_nameNoBrand or company name.
schema_typeNoauto picks the type.auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false. The description adds two genuinely useful facts beyond that: the result is persisted only as a suggestion (not applied to the page), and it consumes 1 AI request, which matters for cost budgeting. It stops short of explaining whether the given URL is fetched live or whether it changes any existing markup.

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?

Two very short statements with the artifact and the cost/state qualifier front-loaded, and no filler. The telegraphic "AI: 1 AI request" fragment is slightly compressed but still readable.

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?

With five parameters, none required, and no output schema, the description leaves an agent unsure what comes back and how the generated suggestion can be retrieved or reviewed. The suggestion/cost details help, but the return side is undocumented for a generator tool.

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 80%, so the schema already documents url, content, brand_name and schema_type. The description restates the type list and the "auto picks the type" behavior rather than adding meaning. It says nothing about the client_id parameter or the relationship between url and content.

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 names the concrete artifact (Schema.org JSON-LD) and enumerates the supported schema types, so an agent can tell this apart from content-writing or meta-tag siblings. The verb is implied rather than stated ("Generate" appears only in the tool name), which keeps it just short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no statement of prerequisites (e.g., whether a crawlable URL is needed), and no named alternative among the many sibling generators. The agent must infer the calling context from the description alone.

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.