Skip to main content
Glama
QuoteNest MCP Server

QuoteNest MCP Server

quotenest_click

Clicks a numbered element on the current QuoteNest page, letting AI agents select controls or records using the element number from the last read.

Instructions

Click a numbered element on the current QuoteNest page.

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": {
      "element": "<element>"
    },
    "name": "quotenest_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden for an action tool with side effects. It says nothing about what a click triggers (navigation, modal, form submission), whether the element numbering from a prior read becomes stale afterward, or what happens on an invalid element number.

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?

A single front-loaded sentence with no filler; the action and its scope are stated immediately. Brevity here is efficient, with the missing content being a completeness issue rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a stateful browser-automation action with no annotations and no output schema, the definition omits what an agent most needs: the post-click page state, whether element numbers are invalidated, and failure behavior. The minimal description is insufficient for a side-effecting interaction 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?

Schema description coverage is 100% and the single parameter is documented as 'Element number from the last read', so the schema already conveys the key constraint. The description's phrase 'numbered element' only echoes this, adding no format, range, or staleness guidance.

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 ('click') and resource ('a numbered element on the current QuoteNest page'), which lets an agent distinguish it from quotenest_type and quotenest_read. It stops short of explicitly contrasting with those siblings, but the action and target are unambiguous.

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?

'On the current QuoteNest page' implies the tool operates on state established by a prior read, but the description never states that an element must first be read, nor when to prefer clicking over typing or navigating by another route. Usage is inferable rather than stated.

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