Iris Works MCP Server

iris_works_open

Opens an Iris Works page in your signed-in Cloud Browser (default app.iris-works.com) to review clients, schedule sessions, and prepare invoices.

Instructions

Open a Iris Works page in your signed-in Cloud Browser (default https://app.iris-works.com) to work with review clients, schedule sessions and prepare invoices.

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": "iris_works_open"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://app.iris-works.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose useful context: the page is opened in a signed-in Cloud Browser session, and the default target is https://app.iris-works.com. It does not say whether the call waits for page load, whether it replaces the current page or opens a new one, or what a failure looks like, which matters for a navigation tool.

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 sentence, front-loaded with the action and target, with the default URL parenthesized where it is easy to scan. The trailing domain examples (review clients, sessions, invoices) are mildly decorative but do help an agent confirm it is on the right tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter navigation tool with no output schema and no annotations, the description covers action, session context, default destination and purpose domain. The remaining gap, load/return behavior, is modest given the tool's simplicity.

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% for the single optional url parameter, and the description only restates the same default value already documented in the schema. It adds no syntax or format guidance beyond what the schema provides, so the baseline 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 names a specific verb (Open) and a specific resource (an Iris Works page), plus the execution context (your signed-in Cloud Browser). That makes it clearly distinct from siblings like iris_works_click, iris_works_read or iris_works_type, which operate on an already-open page. It stops short of an explicit 'not for X' statement, so a 4 rather than 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 Guidelines3/5

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

Usage is only implied: by saying it is for working with review clients, scheduling sessions and preparing invoices, it positions itself as the entry step before read/click/type. There is no explicit when-to-use or when-not-to-use guidance, and no statement such as 'call this first before iris_works_read'. Enough to infer, not enough to be certain.

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

Deploy Server