Skip to main content
Glama

Novig market data (novigapi.com)

start_signup

Create a Novig API account for your user and get a key without a password. Returns approval_url: show it to your user, who approves in one click (free, no card). Then call finish_signup every 5 seconds with device_code. 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": {
      "data_wanted": "<data_wanted>",
      "use_case": "<use_case>"
    },
    "name": "start_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoYour name, such as Claude Code (optional)
detailsNo
found_usNoHow they found us (optional, up to 300)
use_caseYesWhat they will do with it (3-1000, required)
data_wantedYesWhat Novig data your user wants (3-1000 characters, required)
agent_found_usNoHow you, the agent, found us (optional, up to 300)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 well: it discloses the human-approval step, the required return value to surface (approval_url), the polling cadence for the follow-up call, and that there is no charge. It omits failure modes such as expired device codes, re-invocation while a signup is pending, or any rate limits.

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?

Three tight sentences, front-loaded with the action and immediately followed by the result and next step. Minor redundancy: "free, no card" and "Costs nothing" convey the same fact twice.

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?

There is no output schema, so the description must carry the return-value burden; it names approval_url but only implies that the response also supplies device_code, which the user never sees. For a six-parameter mutating signup tool, that and the undocumented nested notes field are the remaining gaps.

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 description coverage is high (83%) and five of six parameters are self-documented in the schema, so the baseline is a 3. The description adds context about why data_wanted and use_case matter by framing the tool as an account request the user must approve, though it never mentions the nested details.notes object or the found_us fields.

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?

States a specific verb and resource ("Create a Novig API account ... get a key without a password") and immediately separates itself from the downstream sibling by saying to call finish_signup afterward. An agent can distinguish this from finish_signup without opening either schema.

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 a clear operating procedure: call this first, show approval_url to the user, then poll finish_signup every 5 seconds with device_code. It removes cost objections up front ("free, no card"). It stops short of explicit exclusions, such as what to do if the user already has an account.

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.