Skip to main content
Glama
QuoteNest MCP Server

QuoteNest MCP Server

quotenest_type

Enter text into a specific numbered field on the current QuoteNest page, such as a quote or client detail, by referencing the field number from the last read.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "quotenest_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It does not say whether existing text is replaced or appended, whether the field must be focused or clicked first, whether typing triggers submission or validation, or what happens on failure — all material for a state-mutating page action.

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 short, front-loaded sentence with no filler or redundant clauses. Its brevity is efficient rather than padded, though it leans toward under-specification that the other dimensions penalize.

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 two-parameter tool with full schema coverage and no output schema, the description is minimally sufficient to attempt a call. However, with no annotations to cover safety or state behavior, it should explain the prerequisite that field numbers come from a prior read and what typing does to existing content.

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%, so both parameters are already documented, including that 'element' is a field number from the last read. The description reinforces that the field is numbered and page-scoped but adds no syntax, ordering, or format detail beyond the schema, 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?

The description gives a specific verb ('Type text') and a specific resource ('a numbered field on the current QuoteNest page'), which is more than a restatement of the name. It stops short of distinguishing itself from the sibling 'quotenest_click', which is the obvious alternative for interacting with a page element, so an agent must infer the division of labor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or named alternative. The phrase 'current QuoteNest page' weakly implies a dependency on prior navigation, but nothing states that a read or open must happen first, nor when clicking is preferred over typing.

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