Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

generate_schema_json

Generate validated Schema.org JSON-LD for SoftwareApplication or Organization, producing accurate structured data while including same_as links only when verified profile URLs are supplied.

Instructions

Generate validated Schema.org JSON-LD structured data for SoftwareApplication or Organization. Pass same_as only with VERIFIED profile URLs (Wikidata Q-item, LinkedIn, GitHub) — links are never invented.

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>",
      "url": "<url>",
      "description": "<description>"
    },
    "name": "generate_schema_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical website URL (e.g., 'https://acme.com')
nameYesOrganization or Software product name
same_asNoVERIFIED external authority profile URLs (Wikidata, LinkedIn, GitHub, Crunchbase). Optional — omitted when not supplied.
descriptionYesHigh-density factual summary of the product or organization
schema_typeNoSchema.org type (default: 'SoftwareApplication')SoftwareApplication

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the output is 'validated' JSON-LD and that same_as links are never invented, but it does not say what happens if an unverified URL is passed (rejected, dropped, error), whether the call is side-effect free, or how validation failures are surfaced.

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?

Two tightly written sentences: the capability first, the high-risk guardrail second. No filler, no repetition of the tool name, and the most failure-prone instruction is placed where an agent will read it.

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?

For a five-parameter generator with no output schema, the description conveys the output format (JSON-LD) and the one constraint most likely to cause bad data. The remaining gap is error/validation behavior, which matters because the tool advertises 'validated' output.

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%, so the baseline is 3. The description reinforces the same_as constraint (verified Wikidata/LinkedIn/GitHub URLs) and the two schema_type values, but adds little beyond what the schema already states for name, url, and description.

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 a specific verb and artifact — generate validated Schema.org JSON-LD structured data — and scopes it to two entity types (SoftwareApplication or Organization). It is clearly distinguishable from the sibling generators (llms.txt, robots.txt), though it never explicitly routes the agent away from them.

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention of when neither entity type fits. The only usage-style instruction ('Pass same_as only with VERIFIED profile URLs') is a parameter rule, not tool-selection guidance.

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