Skip to main content
Glama

Watch company

watch_company

Watch companies. action='start' (the default) starts watching one: at most one alert a day, listing what changed with its sources; entity_id is the one find_company returns (or a Swiss UID), and layers optionally narrows it to a comma-separated list of register, sanctions, regulator (blank watches all). action='list' lists the companies this account watches; action='stop' stops watching the company given by entity_id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "watch_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNostart
layersNo
entity_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Adds real value beyond the annotations by describing the effect of the watch: at most one alert a day, listing what changed with its sources, and the ability to narrow by layer. With readOnlyHint=false and idempotentHint=false already declared, the description could have clarified what happens when starting a watch that already exists or whether stop is reversible - neither is addressed.

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?

Front-loaded verb+resource, then per-action detail separated by semicolons and backticked identifiers, so it reads as a compact reference. It is dense but every clause carries parameter or behavioral information; no filler sentences.

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

Completeness3/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 write semantics of each action are covered. However, gaps remain for a stateful subscription tool with idempotentHint=false and no enums: duplicate-start behavior, whether alerts are the only output, and error conditions are all unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameters and it does: it defines the three action values, states entity_id's accepted forms (find_company id or Swiss UID), and explains layers as a comma-separated list of register, sanctions, regulator with blank meaning all. This fully compensates for the absent schema descriptions and the missing enum on action.

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 the resource (companies) and then enumerates the three distinct operations - start watching (default), list watched, and stop watching - so the agent knows exactly what the tool does. It also names find_company as the source of entity_id, which anchors it against a sibling, though it says nothing about company_file.

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?

Gives clear operational context: 'start' is the default action, entity_id comes from find_company (or a Swiss UID), and 'stop' requires entity_id. That effectively routes the agent to find_company first. It stops short of stating when not to use this tool or how it relates to company_file.

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.