Skip to main content
Glama

workquote_click

Clicks a numbered element on the current WorkQuote page using the element number from the last read.

Instructions

Click a numbered element on the current WorkQuote 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": "workquote_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.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden and it does not disclose what a click implies: whether the page navigates or re-renders, whether element numbering becomes stale after a click, how waits/timeouts work, or what happens on an invalid index. For a browser-mutating action this is a meaningful gap.

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 tight sentence with the action front-loaded and zero filler. Nothing could be removed without losing meaning.

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?

Adequate for a one-parameter interaction tool, but with no annotations and no output schema the description should explain post-click state and whether the element index remains valid. It leaves an agent able to call the tool but unsure what to expect afterward.

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 does the heavy lifting. The description only restates 'numbered element' without adding format, range, or staleness semantics.

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 WorkQuote page'), which is enough to distinguish it from the type/read/open/close siblings by verb alone. It stops short of explicitly contrasting against workquote_type or workquote_read, so not a 5.

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 when-to-use or when-not-to-use guidance, and no alternative is named. The only sequencing hint ('from the last read') lives in the schema, not the description, so an agent must infer that a read must precede a click and that other interaction tools are the alternative.

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