Skip to main content
Glama
Sign In
ai.backskills/backskills

ai.backskills/backskills

by domco685
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

watch

Monitor skills your agent depends on and optionally send a webhook when they change.

Instructions

Watch skills you depend on; optional webhook

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": {
      "skills": "<skills>"
    },
    "name": "watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillsYes
webhookNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints at an ongoing watch and optional webhook but does not disclose side effects, persistence, notification semantics, permissions, or idempotency.

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?

The description is a single short sentence with no wasted words and is front-loaded. It is concise, though its terseness contributes to under-specification rather than clarity.

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

Completeness2/5

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

With no annotations, no output schema, and 0% schema description coverage, the definition should do more to explain behavior and parameters. It identifies the basic action but leaves key operational details missing.

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 description coverage is 0%, so the description must compensate. It mentions 'skills' and 'optional webhook', but adds no format details, array expectations, or explanation of what the webhook URL receives or triggers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource: 'Watch skills you depend on' with an 'optional webhook'. However, 'watch' is ambiguous and the definition does not distinguish this tool from siblings like list_watches or changes.

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 guidance, no exclusions, and no mention of alternatives such as list_watches or changes. The phrase 'skills you depend on' implies a context but does not explain when to choose this tool.

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