Skip to main content
Glama

Article structured data

bpj_article_structured_data
Read-onlyIdempotent

Validate article dates and author details and generate Article JSON-LD.

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": {
      "headline": "<headline>",
      "url": "<url>",
      "author": "<author>",
      "published": "<published>",
      "modified": "<modified>"
    },
    "name": "bpj_article_structured_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
authorYes
headlineYes
modifiedYes
publishedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that validation occurs, without saying what happens on invalid dates or bad author data (error vs. warning), and with no output schema it does not describe the shape of the returned JSON-LD — a significant gap for a generator/validator.

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?

A single front-loaded sentence with no filler or redundancy. It is terse rather than padded, though the terseness comes at the cost of the missing behavioral detail scored elsewhere.

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 five required parameters, no output schema, and no param descriptions, the description is too thin to prepare an agent for correct invocation. It should at minimum state the expected date format handling, what validation failures look like, and roughly what JSON-LD is produced.

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 0% (only titles, e.g. 'Modified date YYYY-MM-DD', carry hints). The description mentions dates and author but says nothing about headline or url, the two params most tied to JSON-LD correctness, and gives no format constraints beyond what titles already imply.

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 two concrete actions (validate dates/author details, generate Article JSON-LD) and a specific resource, which distinguishes it from structured-data siblings like bpj_faq_structured_data and bpj_breadcrumb_structured_data. It does not explicitly name those siblings, but the verb+resource pairing is clear enough for an agent to identify scope.

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 guidance, no prerequisites, and no exclusions or alternatives. An agent must infer from the name alone that this is the tool for Article-type JSON-LD rather than FAQ, breadcrumb, or other structured data.

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.