Skip to main content
Glama
QuoteNest MCP Server

QuoteNest MCP Server

quotenest_guide

Call this first to learn how QuoteNest works: screens, quote and invoice flows, and the sign-in link, so you can handle cleaning and pressure washing jobs inside the app.

Instructions

How to work in QuoteNest (cleaning and pressure washing quotes, proposals, invoices and repeat bookings): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in QuoteNest, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses content scope (screens, sign-in link) and ordering behavior, and the tool is inherently informational, but it never says what is actually returned — prose instructions, a URL, structured steps — or whether any workspace/account context is required.

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 compact sentences with zero filler; the domain scope in parentheses earns its place by telling the agent what business context the guide covers. Placing "Call this first" at the end is slightly weaker than front-loading it, but it still reads cleanly.

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?

For a single-optional-parameter, no-output-schema orientation tool, the description covers what it contains and when to call it. The only meaningful omission is the return format, which matters because the agent cannot otherwise tell whether it receives steps, a link, or a screen list.

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?

There is one optional parameter and schema description coverage is 100%, with the schema already explaining "task" as what you want done in QuoteNest in your own words. The description adds no additional meaning about how to phrase the task or how it influences the returned guidance, so the baseline of 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 resource (guidance on how to work in QuoteNest) and enumerates the coverage: screens and the sign-in link, scoped to cleaning/pressure-washing quotes, proposals, invoices and repeat bookings. It is clearly the orientation/documentation tool rather than an action tool like quotenest_click or quotenest_open, though it never explicitly contrasts itself with them.

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?

"Call this first" is an explicit and unambiguous sequencing instruction that tells the agent when to invoke this tool relative to the others. There are no when-not conditions, but for an orientation tool that is a minor gap.

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