Skip to main content
Glama
CorgiCorner

Bisibility

by CorgiCorner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Disable sitemap monitor

disable_sitemap_monitor

Disable a project's sitemap monitor to stop tracking while retaining its existing snapshots.

Instructions

Disable the project sitemap monitor while retaining its existing snapshots.

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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description usefully adds that existing snapshots are retained — a real behavioral guarantee not derivable from the structured fields. It does not address idempotency-key replay semantics or the reversal path, so it falls short of a 5.

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?

One sentence, front-loaded with the action and followed by the important side-effect qualifier. Nothing is wasted and nothing is buried.

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 simple three-parameter mutation with annotations covering the safety profile and no output schema, the description is nearly sufficient — the retention guarantee is the key thing an agent needs. It is only slightly thin on the idempotency contract and reversal tooling.

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 coverage is 67%: monitor_id and project_id are documented in the schema, but idempotency_key has no description anywhere, and the description text says nothing about any parameter. The description does not compensate for the coverage gap, so it sits below the high-coverage baseline of 3.

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 (disable) and resource (the project sitemap monitor), so the agent knows exactly what happens. The distinction from enable_sitemap_monitor is obvious from the verb, though the description never names or contrasts the 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 Guidelines2/5

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

There is no when-to-use/when-not guidance, no prerequisites (e.g. permissions), and no pointer to enable_sitemap_monitor as the reversal path. Usage is only implied by the verb.

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