Skip to main content
Glama

Novig market data (novigapi.com)

finish_signup

Collect the API key after your user approved at approval_url. Poll every 5 seconds with device_code. Pending returns AUTHORIZATION_PENDING; the key is returned once. Costs nothing.

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": {
      "device_code": "<device_code>"
    },
    "name": "finish_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_codeYesnvd_... from start_signup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load and does well: it discloses the polling cadence, the AUTHORIZATION_PENDING response, the one-time nature of key retrieval, and that the call is free. It omits other error states and expiry behavior, which keeps 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?

Four tight sentences, each front-loading a distinct fact (prerequisite, polling cadence, pending semantics plus one-time retrieval, cost). No filler and nothing redundant.

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?

With no output schema, the description must explain returns, and it does: the key is returned once and pending yields AUTHORIZATION_PENDING. It leaves other failure modes unaddressed, which is the main remaining gap for a polling tool.

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?

Only one parameter, and schema coverage is 100% with the description already naming device_code and its origin in start_signup. The description adds lifecycle context but no format or handling detail beyond what the schema provides, so baseline 3 applies.

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 ('Collect the API key') and ties it to the lifecycle started by start_signup via the device_code. It is clear what the tool does, though the sibling relationship is implied through the parameter rather than stated as an explicit alternative.

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 concrete when-to-use conditions: call after the user approves at approval_url, and poll every 5 seconds. It does not enumerate what to do on non-pending errors or when the device code expires, so guidance is clear but not exhaustive.

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.