Skip to main content
Glama

Novig market data (novigapi.com)

get_watchlists

Read one of your Watchlists by id.

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": {
      "id": "<id>",
      "user_request": "<user_request>"
    },
    "name": "get_watchlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
user_requestYesThe current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it offers almost none: nothing about whether the id must belong to the caller, what happens on an unknown id, permission requirements, or what the response contains. "your Watchlists" hints at a per-user scope but is not elaborated.

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?

A single short sentence with no filler, and the resource and scoping key are front-loaded. Its brevity is efficient rather than padded, though it edges toward under-specification.

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 an undocumented required id parameter, the definition leaves an agent without the information needed to call it confidently or interpret a result. A read-only retrieval tool needs at least the id's origin and the returned resource shape.

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 coverage is 50%: user_request is documented in-schema, but id has no description. The description's only contribution is "by id", which does not add format, source, or constraint detail for the undocumented id parameter. This fails to compensate for the coverage gap.

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 ("Read ... Watchlists") scoped by id, which is enough to distinguish it from create/delete/update/list siblings. It stops short of naming those siblings explicitly, so the separation relies on the verb.

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

Usage Guidelines3/5

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

"by id" implies the caller must already hold a watchlist identifier, but the description never says where that id comes from (e.g., list_watchlists) or when to prefer this over list_watchlists. Usage is only implied.

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.