Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

get_remediation_patch

Generates the exact zero-touch patch for robots.txt, llms.txt, and Schema JSON-LD files, enabling AI coding agents to write and deploy them directly into the local workspace repository.

Instructions

Get the exact zero-touch file patch (public/robots.txt, public/llms.txt, Schema JSON-LD) for a website. Enables AI coding agents like Claude Code, Cursor, Windsurf, or ChatGPT to write and deploy these files directly into the local workspace repository with zero manual copy-pasting.

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

Input Schema

NameRequiredDescriptionDefault
domainYesWebsite domain name (e.g. 'example.com')
frameworkNoTarget web framework: 'nextjs', 'astro', 'remix', 'hugo', or 'generic_html' (default: 'generic_html')generic_html
brand_nameNoOptional brand/product name

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose what the payload contains (exact file contents for three paths) and that it is intended for direct deployment with 'zero manual copy-pasting', which implies this is a retrieval, not a write, operation. It does not state the return shape, whether framework choice alters the content, or any auth/rate constraints.

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 sentences, front-loaded with the concrete deliverable and file paths before the audience framing. The second sentence leans promotional ('zero manual copy-pasting') but still conveys the intended consumer, so it earns most of its place. No redundancy.

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 no annotations and no output schema, the description should clarify what the returned 'patch' looks like — file-to-content mapping, a diff, or a zip — and it does not, leaving the agent unsure how to consume the result. It covers intent and scope adequately but leaves the return contract underspecified for a 3-parameter 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 100%, so domain, framework (with default and value list), and brand_name are already documented in the schema. The description adds no parameter-level meaning beyond that — it never explains how 'framework' changes the emitted patch, which is the one genuinely non-obvious semantic. Baseline 3 is appropriate when the schema does the work.

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 ('Get') and a concrete resource: a 'zero-touch file patch' enumerating public/robots.txt, public/llms.txt, and Schema JSON-LD for a website. An agent can tell this is a combined multi-file remediation artifact rather than a single-file generator. It stops short of naming the sibling tools (generate_robots_txt, generate_llms_txt, generate_schema_json) it overlaps with, so differentiation is only implied.

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?

The second sentence establishes the operating context — an AI coding agent writing and deploying files into a local workspace repository — which implies when this tool is a fit. However, there is no explicit when-not guidance and no alternatives named, even though three sibling tools appear to generate the same artifacts individually. The agent must infer selection from the file list alone.

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