Skip to main content
Glama

Novig market data (novigapi.com)

rate_result

Rate how well the last result served your user's task, 1 to 5, with an optional message. The team reads every one. Costs nothing and works while rate limited. Leave out secrets and personal data.

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": "rate_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
agentNo
ratingNo
messageNo
blockingNo
endpointNo
use_caseNo

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?

With no annotations, the description carries the full burden and does reasonably well: it discloses that the call is free, that it functions under rate limiting, that submissions are human-reviewed, and that secrets/personal data must be omitted. It does not state whether a prior result is required to have occurred in-session or what the call returns on success, but for a fire-and-forget feedback call the substantive risks are covered.

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 short sentences, front-loaded with the action and scale, then value ('the team reads every one'), then practicality ('costs nothing and works while rate limited'), then the safety caveat. Nothing is padded and each sentence adds a distinct fact.

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?

The action, scale, motivation, and privacy constraint are all present, which is adequate for a simple feedback tool with no output schema. However, with seven completely undescribed optional parameters, an agent cannot confidently fill in 'kind', 'endpoint', or 'use_case' from this definition alone, so it is only minimally sufficient for the tool's schema complexity.

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?

Seven parameters at 0% schema description coverage, and the description only accounts for two of them: 'rating 1 to 5' (which merely restates the schema's minimum/maximum) and the 'optional message'. The enum parameter 'kind', plus 'agent', 'blocking', 'endpoint', and 'use_case', are entirely unexplained anywhere, leaving an agent to guess what 'endpoint' or 'use_case' should contain.

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?

Names a specific verb and resource: rate 'how well the last result served your user's task' on a 1-5 scale with an optional message. That is unmistakably a feedback tool and cannot be confused with any of the sibling data-retrieval tools (get_results, search, fair_price, etc.).

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 when-to-use context: after the agent has produced a result for the user, and notably 'works while rate limited', which tells the agent this stays callable in a degraded state. It stops short of explicit exclusions (e.g., do not rate results you did not produce), so it falls just short of the top band.

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.