Skip to main content
Glama

create_watch

Register webhook watches for AI model price changes, service status transitions, daily/weekly pricing digests, or leaderboard rank movements. Receive HMAC-signed POST notifications to your callback URL.

Instructions

Register a webhook watch. type selects what to watch: "price" (a model price change), "status" (a service status transition), "digest" (a scheduled daily or weekly pricing summary), or "leaderboard_rank" (a provider crossing an uptime-rank threshold). Costs 1 credit ($0.02) at registration; the watch lives 90 days and each fire is an HMAC-signed POST to callback_url. Needs a TENSORFEED_TOKEN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesWhat to watch.
callback_urlYesHTTPS URL that receives the HMAC-signed POST when the watch fires.
secretNoOptional shared secret used to HMAC-sign delivery bodies.
modelNotype=price only. Model name (e.g. "Claude Opus 4.7").
fieldNotype=price only. Which price field to watch.
cadenceNotype=digest only. How often the digest fires.
providerNotype=status or type=leaderboard_rank only. Provider name or slug (case-insensitive). e.g. anthropic, openai, gemini, bedrock, azure.
opNotype=price uses lt/gt/changes (lt = below threshold, gt = above, changes = any change). type=status uses becomes/changes (becomes = transitions to a specific value; changes = any transition). type=leaderboard_rank uses drops_below/rises_above/changes (rank 1 = best; drops_below: was rank<=N now rank>N; rises_above: was rank>=N now rank<N; changes: any rank movement).
thresholdNotype=price (when op is lt or gt) or type=leaderboard_rank (when op is drops_below or rises_above). Integer rank position for leaderboard_rank.
valueNotype=status only. Required when op is becomes.
Behavior5/5

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

The description goes beyond annotations by detailing the cost (1 credit/$0.02), lifetime (90 days), delivery mechanism (HMAC-signed POST to callback_url), and authentication requirement (TENSORFEED_TOKEN). No contradiction with annotations.

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?

The description is concise (four sentences) and front-loaded with the primary purpose. Each sentence provides essential information: registering a watch, type options, cost/lifetime/auth, and fire mechanism. No redundant text.

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?

Given 10 parameters (2 required), rich schema, and no output schema, the description covers the core concepts, constraints, and behavioral traits well. It could mention the response format (e.g., watch ID) but is otherwise thorough.

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?

Schema coverage is 100%, but the description adds value by explaining the meaning of the 'type' enum and how other parameters relate to each type (e.g., 'model' and 'field' for type=price, 'provider' for status/leaderboard_rank). This supplements the schema descriptions.

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

Purpose5/5

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

The description starts with 'Register a webhook watch,' clearly stating the verb and resource. It then elaborates on what types can be watched (price, status, digest, leaderboard_rank), which distinguishes it from sibling tools like delete_watch or list_watches.

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?

The description provides clear context on when to use the tool: to register a webhook watch for different event types. It explains each type's purpose but does not explicitly mention when not to use it or contrast with alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RipperMercs/tensorfeed-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server