Skip to main content
Glama
QuoteNest MCP Server

QuoteNest MCP Server

quotenest_status

Check whether your Cotlet.dev account and QuoteNest connection are ready, including account status, available credits, and QuoteNest access.

Instructions

Check that your Cotlet.dev account and QuoteNest are ready: account, credits and QuoteNest connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. "Check" implies a harmless read, and it names the three things inspected (account, credits, connection), but it never states whether it reports per-item pass/fail, raises an error on failure, or requires authentication to run.

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?

One front-loaded sentence with the action first and the inspected items enumerated after the colon; no filler. The colon list is slightly dense but every clause carries information.

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?

For a zero-parameter diagnostic with no output schema and no annotations, the description covers what is inspected but not what comes back or how failures surface. It is sufficient to select the tool but thin for interpreting its result.

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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema. Baseline 4 applies; the description correctly avoids inventing parameters.

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?

The description uses a specific verb ("Check") plus a concrete resource set (Cotlet.dev account, credits, QuoteNest connection), so an agent knows this is a readiness/diagnostic call rather than a UI action. It implicitly separates itself from the click/open/type siblings, though it never names them.

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?

Usage is only implied: "Check that ... are ready" suggests calling it before attempting other QuoteNest operations, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the precondition role from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.