Skip to main content
Glama
jakeyoung1

veris

by jakeyoung1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage Watches (change-detection)

watch_manage

Add, remove, or list watches. Watch a company's SEC filings (target = ticker/name/CIK, optional formType like 8-K) or any URL (target = https://…, watched by content hash).

Instructions

Add, remove, or list watches. Watch a company's SEC filings (target = ticker/name/CIK, optional formType like 8-K) or any URL (target = https://…, watched by content hash). Adding baselines current state; use watch_check later to see only what's new. By default only MATERIAL forms alert (8-K, 10-K/Q, 13D/G, mergers, offerings, late filings) — routine Form 4 / 13F noise is suppressed. Pass formType="ALL" to alert on every form.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhat to do
targetNoTicker/name/CIK, URL, or watch id (for remove)
formTypeNoForm filter for filings watches. Omit for the material-forms default, "ALL" for every form, or a specific form like "8-K".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • changedInput schema / properties / formType / description
      Previous value: -"Optional form filter for filings watches, e.g. \"8-K\""New value: +"Form filter for filings watches. Omit for the material-forms default, \"ALL\" for every form, or a specific form like \"8-K\"."
  2. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: adding baselines rather than backfilling alerts, content-hash watching for URLs, and a documented materiality filter that suppresses routine Form 4/13F noise unless formType="ALL". It omits auth/permission requirements, watch-count limits, and what happens on duplicate watches, keeping it 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?

Operations are front-loaded in the first four words, followed by watch-kind semantics, the add/check workflow, and the default filter. Every sentence earns its place; the material-forms parenthetical is long but is the tool's key behavioral fact.

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 3-parameter, no-output-schema tool, the description covers the action set, target formats, the default filter and its override, and the hand-off to watch_check. Missing only ancillary facts — permissions, persistence/limits on stored watches, and remove-by-id behavior beyond the schema note.

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 already 100%, so the baseline is 3; the description earns a bump by enumerating the material forms (8-K, 10-K/Q, 13D/G, mergers, offerings, late filings) that the schema only gestures at with 'the material-forms default', and by restating target's accepted formats (ticker/name/CIK, https://, watch id).

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?

Starts with a specific triple-verb (Add, remove, list) over a named resource (watches), then narrows to the two watch kinds: SEC filings and URLs. An agent can immediately tell this is the watch-creation/management tool and not the checking tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: add baselines the current state and 'use watch_check later to see only what's new' — naming the sibling and the condition that selects it. The formType default/ALL switch is also framed as a usage decision, leaving nothing to inference.

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