Skip to main content
Glama
QuoteNest MCP Server

QuoteNest MCP Server

quotenest_read

Reads the current QuoteNest page to return its text and numbered buttons, links, and fields, optionally scoped to a specific element.

Instructions

Read the current QuoteNest page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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 burden; it does clearly signal a non-mutating read of the live page and what content categories come back. However it says nothing about behavior on long pages (truncation/pagination), whether element numbers are stable across calls, or what happens when no page is open. Those gaps matter for a page-scraping tool.

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?

One front-loaded sentence with zero filler; the verb and target come first, the payload enumeration second. Nothing to trim.

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 simple one-optional-param read tool with no output schema, the description adequately conveys what comes back. It omits the precondition (an open page), the meaning/utility of the element scope, and failure modes, which an agent would need to call it confidently.

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 coverage is 100% and the single parameter is well documented in the schema ("Read only inside this element."). The description adds no meaning about the element parameter — why scoping helps, what the integer refers to, or interplay with the numbered output. Baseline 3 applies given full schema coverage.

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 ("Read") and object ("the current QuoteNest page") and enumerates the returned content: text, numbered buttons, links and fields. That enumeration effectively distinguishes it from quotenest_click/quotenest_type, which operate on those numbered elements. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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?

The word "current" implies a page must already be open, and reading before interacting is the obvious workflow, but the description never states when to call this versus quotenest_status or quotenest_guide, nor any exclusion. Usage is inferred rather than stated.

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