Skip to main content
Glama

monograph_click

Click a numbered element on the current Monograph page to navigate screens or select controls during guided project, staffing, budget, time, or billing tasks.

Instructions

Click a numbered element on the current Monograph 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": "monograph_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 supplied, so the description carries the full burden. It says nothing about what the click causes (navigation, form submission, page reload), whether the element index becomes stale after the click, or what happens if the element is missing or the page state has changed.

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 front-loaded sentence with no filler, and the target and scope appear immediately. It is arguably under-specified rather than verbose, so nothing needs trimming.

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-parameter action tool with no output schema, the definition is minimally sufficient: an agent knows to pass an element number for the active page. It is still missing state preconditions and post-click effects, which matter for a UI automation tool where element indices depend on prior reads.

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?

With a single parameter at 100% schema description coverage, the schema already explains that the integer is an element number from the last read. The description's use of 'numbered element' reinforces this but adds no format, range, or staleness semantics beyond the schema.

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 and target: clicking a numbered element on the current Monograph page. That is distinguishable from siblings like monograph_read, monograph_type and monograph_open, though the description 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 Guidelines3/5

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

The phrase 'current Monograph page' implies a page must already be open, and the schema's 'number from the last read' hints at a read-then-click sequence. However, no when-to-use/when-not guidance is given, and it never says to prefer monograph_type when entering text rather than activating a numbered element.

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