Skip to main content
Glama
Sign In
docs-publisher

docs-publisher

by ArfZkwn-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

deploy_site

Rebuilds and publishes the documentation website to make tutorial changes on the docs branch go live. Run it after publishing, editing, or deleting tutorials.

Instructions

Rebuild the documentation website and publish it, so tutorials on the docs branch go live. Call it after publishing, editing or deleting tutorials. Takes a minute or two.

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": "deploy_site"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does so reasonably: it states the operation rebuilds and publishes publicly visible content, sources from the docs branch, and takes "a minute or two" — useful latency guidance for an agent. It says nothing about failure modes or whether a failed rebuild leaves the site in a partial state.

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 sentences, front-loaded with the action, then the trigger and the timing note. Every clause adds information an agent needs; nothing is redundant.

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

Completeness5/5

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

For a zero-param, no-output-schema, unannotated tool, the description supplies the trigger, the effect, the content source, and expected duration. There is no structured field left uncovered that an agent would need before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies the operation is parameterless and acts on implicit state (the docs branch).

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?

"Rebuild the documentation website and publish it" is a specific verb+resource pair, and the clause about tutorials on the docs branch scopes what content gets deployed. It implicitly separates itself from publish_tutorial by describing the site build rather than a single tutorial, but it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Call it after publishing, editing or deleting tutorials" gives a concrete trigger condition tied to the sibling tools. There is no explicit exclusion or statement that it should not be called for other changes (e.g., image-only updates), so it stops short of the top score.

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

Deploy Server

Other Tools