Skip to main content
Glama

hallux_watch

Register identifiers for a signed webhook when their verdict changes: phantom -> squat (someone registered a name models invent) or absent -> exists. Use for a name that came back absent/phantom which the user still intends to use, or a dependency set worth monitoring. Requires an API key; costs 25 credits ($0.02) per identifier per 30 days.

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": {
      "identifiers": "<identifiers>",
      "callbackUrl": "<callbackUrl>"
    },
    "name": "hallux_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
callbackUrlYesPublic https URL to POST transitions to.
identifiersYes

Output Schema

NameRequiredDescriptionDefault
buyNo
errorNo
renewsNo
secretNoShown once. HMAC key for X-Hallux-Signature.
chargedNo
creditsNo
messageNo
watchIdNo
paidUntilNo
callbackUrlNo
identifiersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / identifiers / items / properties / namespace / description
      Previous value: -"pkg.npm, pkg.pypi, pkg.crates, pkg.go, pkg.maven (group:artifact), pkg.nuget, pkg.rubygems, pkg.packagist (vendor/name), pkg.hex, pkg.pub, img.docker, repo.github (owner/repo), cite.doi"New value: +"Covered: pkg.npm, pkg.pypi, pkg.crates, pkg.go, pkg.maven (group:artifact), pkg.nuget, pkg.rubygems, pkg.packagist (vendor/name), pkg.hex, pkg.pub, img.docker, repo.github (owner/repo), cite.doi. Other dotted namespaces return verdict unknown with reason namespace_unsupported and are not charged."
    • removedInput schema / properties / identifiers / items / properties / namespace / enum
      Removed value: -[
      -  "pkg.npm",
      -  "pkg.pypi",
      -  "pkg.crates",
      -  "pkg.go",
      -  "pkg.maven",
      -  "pkg.nuget",
      -  "pkg.rubygems",
      -  "pkg.packagist",
      -  "pkg.hex",
      -  "pkg.pub",
      -  "img.docker",
      -  "repo.github",
      -  "cite.doi"
      -]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "buy": {
      +      "type": "string"
      +    },
      +    "callbackUrl": {
      +      "type": "string"
      +    },
      +    "charged": {
      +      "type": "integer"
      +    },
      +    "credits": {
      +      "type": "integer"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "identifiers": {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "paidUntil": {
      +      "type": "string"
      +    },
      +    "renews": {
      +      "type": "string"
      +    },
      +    "secret": {
      +      "description": "Shown once. HMAC key for X-Hallux-Signature.",
      +      "type": "string"
      +    },
      +    "watchId": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed8 schema fields changed
    • changedInput schema / properties / callbackUrl / description
      Previous value: -"An https URL to POST transitions to."New value: +"Public https URL to POST transitions to."
    • removedInput schema / properties / identifiers / description
      Removed value: -"Up to 100 identifiers to watch, typically ones that came back absent or phantom."
    • addedInput schema / properties / identifiers / items / additionalProperties
      Added value: +false
    • changedInput schema / properties / identifiers / items / properties / namespace / description
      Previous value: -"Where the identifier lives: pkg.npm, pkg.pypi, pkg.crates, pkg.go, pkg.maven or pkg.nuget for a package, cite.doi for a DOI."New value: +"pkg.npm, pkg.pypi, pkg.crates, pkg.go, pkg.maven (group:artifact), pkg.nuget, pkg.rubygems, pkg.packagist (vendor/name), pkg.hex, pkg.pub, img.docker, repo.github (owner/repo), cite.doi"
    • changedInput schema / properties / identifiers / items / properties / namespace / enum
      Previous value: -[
      -  "cite.doi",
      -  "pkg.crates",
      -  "pkg.go",
      -  "pkg.maven",
      -  "pkg.npm",
      -  "pkg.nuget",
      -  "pkg.pypi"
      -]New value: +[
      +  "pkg.npm",
      +  "pkg.pypi",
      +  "pkg.crates",
      +  "pkg.go",
      +  "pkg.maven",
      +  "pkg.nuget",
      +  "pkg.rubygems",
      +  "pkg.packagist",
      +  "pkg.hex",
      +  "pkg.pub",
      +  "img.docker",
      +  "repo.github",
      +  "cite.doi"
      +]
    • changedInput schema / properties / identifiers / items / properties / value / description
      Previous value: -"The identifier exactly as written, e.g. requests, @types/node, github.com/spf13/cobra, 10.1038/nature12373."New value: +"Exactly as written, e.g. requests, @types/node, github.com/spf13/cobra, org.slf4j:slf4j-api, 10.1038/nature12373"
    • addedInput schema / properties / identifiers / items / properties / version
      Added value: +{
      +  "description": "Optional exact version to verify. Models invent versions too.",
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "decision": {
      -      "enum": [
      -        "WATCHING"
      -      ],
      -      "type": "string"
      -    },
      -    "event": {
      -      "type": "string"
      -    },
      -    "registered": {
      -      "items": {
      -        "properties": {
      -          "namespace": {
      -            "type": "string"
      -          },
      -          "reason": {
      -            "type": "string"
      -          },
      -          "signingSecret": {
      -            "description": "Verifies the webhook signature.",
      -            "type": "string"
      -          },
      -          "value": {
      -            "type": "string"
      -          },
      -          "watchId": {
      -            "type": "string"
      -          },
      -          "watched": {
      -            "type": "boolean"
      -          }
      -        },
      -        "required": [
      -          "namespace",
      -          "value",
      -          "watched"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "signature": {
      -      "properties": {
      -        "format": {
      -          "type": "string"
      -        },
      -        "header": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "transitionOfInterest": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "decision",
      -    "registered"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. Changed4 schema fields changed
    • addedInput schema / properties / identifiers / description
      Added value: +"Up to 100 identifiers to watch, typically ones that came back absent or phantom."
    • addedInput schema / properties / identifiers / items / properties / namespace / description
      Added value: +"Where the identifier lives: pkg.npm, pkg.pypi, pkg.crates, pkg.go, pkg.maven or pkg.nuget for a package, cite.doi for a DOI."
    • addedInput schema / properties / identifiers / items / properties / value / description
      Added value: +"The identifier exactly as written, e.g. requests, @types/node, github.com/spf13/cobra, 10.1038/nature12373."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "decision": {
      +      "enum": [
      +        "WATCHING"
      +      ],
      +      "type": "string"
      +    },
      +    "event": {
      +      "type": "string"
      +    },
      +    "registered": {
      +      "items": {
      +        "properties": {
      +          "namespace": {
      +            "type": "string"
      +          },
      +          "reason": {
      +            "type": "string"
      +          },
      +          "signingSecret": {
      +            "description": "Verifies the webhook signature.",
      +            "type": "string"
      +          },
      +          "value": {
      +            "type": "string"
      +          },
      +          "watchId": {
      +            "type": "string"
      +          },
      +          "watched": {
      +            "type": "boolean"
      +          }
      +        },
      +        "required": [
      +          "namespace",
      +          "value",
      +          "watched"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "signature": {
      +      "properties": {
      +        "format": {
      +          "type": "string"
      +        },
      +        "header": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "transitionOfInterest": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "decision",
      +    "registered"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds material context beyond the annotations: authentication requirement (API key), per-identifier metered cost (25 credits / $0.02 per 30 days), and the notification mechanism (signed POST on verdict transition). It does not state whether re-registering duplicates a watch (annotations say idempotentHint=false) or how/can a watch be cancelled, which are real gaps for a mutating subscription tool.

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?

Three tightly packed sentences, each earning its place: behavior, usage conditions, then cost/auth constraints front-loaded in that order. No restatement of the name or redundant framing.

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?

An output schema exists so return values need no explanation, and the description covers triggering conditions, auth, and pricing adequately for a 2-parameter tool. Lifecycle details (cancellation, duplicate registration, watch expiry tied to the 30-day billing window) are the remaining omission.

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 50%, but the schema itself richly documents namespace coverage, exact value formatting, and optional version verification, and callbackUrl is explained as a public HTTPS POST target. The description only adds that cost accrues per identifier; it does not clarify the callback payload, retry behavior, or the per-identifier billed period at the parameter level.

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 ('Register identifiers for a signed webhook') and defines exactly which state transitions trigger it (phantom -> squat, absent -> exists), which inherently separates it from one-off check tools. It stops short of naming a sibling like hallux_check as the contrasting alternative, so it lands just under a 5.

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?

'Use for a name that came back absent/phantom which the user still intends to use, or a dependency set worth monitoring' gives clear, actionable selection criteria. It implies but never explicitly states that a single verification should go to hallux_check instead, so exclusions are inferred rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources