Skip to main content
Glama
CorgiCorner

Bisibility

by CorgiCorner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Enable sitemap monitor

enable_sitemap_monitor

Turn on a project's sitemap monitor so the next scheduled worker sync fetches the sitemap; enabling does not trigger an immediate fetch.

Instructions

Enable the project sitemap monitor. The next scheduled worker sync fetches the sitemap; enabling does not fetch immediately.

Input Schema

NameRequiredDescriptionDefault
monitor_idNoIdentifier of the sitemap monitor to update, as returned by list_sitemap_monitors. Optional: a project has one monitor whose id equals the project id, so it defaults to project_id.
project_idYesIdentifier of the bisibility project to operate on; list_projects returns valid project ids.
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.1
    • changedInput schema / properties / monitor_id / description
      Previous value: -"Identifier of the bisibility project to operate on; list_projects returns valid project ids."New value: +"Identifier of the sitemap monitor to update, as returned by list_sitemap_monitors. Optional: a project has one monitor whose id equals the project id, so it defaults to project_id."
    • changedInput schema / required
      Previous value: -[
-  "monitor_id",
-  "project_id"
-]New value: +[
+  "project_id"
+]
  2. First observedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

The description adds genuinely non-obvious behavior beyond the annotations: enabling is deferred to the next scheduled worker sync rather than triggering an immediate fetch. Annotations only cover safety (readOnlyHint=false, destructiveHint=false), so this scheduling disclosure is the valuable addition, though it omits idempotency semantics and error behavior.

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 short sentences, zero filler, and the deferred-fetch caveat is placed immediately after the action statement so it cannot be missed. Nothing to trim.

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?

No output schema exists and annotations only cover the safety profile, so the description carries the rest. It covers the key timing behavior but omits prerequisites, idempotency_key semantics, and outcomes such as an already-enabled monitor. Sufficient to call correctly, not complete.

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 coverage is 67%, and the schema itself richly documents monitor_id (including its default to project_id) and project_id. The description adds nothing about parameters, and idempotency_key has no description at all in either place, so the baseline 3 for mid coverage is appropriate.

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?

States a specific verb and resource ('Enable the project sitemap monitor'), so the agent immediately knows this toggles the monitor on. It does not explicitly name the counterpart disable_sitemap_monitor, but the verb makes the direction of the toggle unambiguous without opening a schema.

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?

Usage is implied by the verb 'enable' rather than stated: there is no guidance on prerequisites (a configured sitemap, an existing monitor), no mention of disable_sitemap_monitor as the inverse, and no note on what happens if the monitor is already enabled. Adequate but with clear gaps for a state-changing toggle.

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