Skip to main content
Glama
Sign In
Iris Works MCP Server

Iris Works MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

iris_works_click

Click a numbered element on the current Iris Works page by providing its element number from the last page read.

Instructions

Click a numbered element on the current Iris Works 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": "iris_works_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 are provided, so the description carries the full burden, yet it never says what a click does — whether it navigates, submits a form, triggers a purchase, or is reversible. For an interaction tool that can cause side effects on a live page, this leaves the agent unable to judge risk.

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 or redundancy. Its brevity is a virtue structurally, though the thinness is penalized elsewhere rather than here.

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?

A page-mutating interaction tool with no annotations, no output schema, and a one-line description that omits what happens after the click, whether element numbers expire, and how failures (stale index) are reported. It is not complete enough for an agent to invoke 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 already documents itself as "Element number from the last read" with a minimum of 1. The description's "numbered element" merely restates the schema, adding no further meaning about valid ranges or staleness of element numbers.

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 a specific target ("a numbered element on the current Iris Works page"), which distinguishes it from read/type/status siblings by implication. It stops short of explicitly naming which sibling to use when, so it is clear but not fully differentiating.

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?

Usage is only implied: "on the current Iris Works page" suggests a page must already be open, and "numbered element" hints at a prior read. No explicit when-to-use, prerequisites, or alternatives (e.g., iris_works_read to obtain element numbers) are stated in the description itself.

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

Deploy Server

Other Tools