Skip to main content
Glama

monograph_open

Open a Monograph page in your signed-in Cloud Browser to manage architecture and engineering firm projects, staffing, budgets, time, and billing.

Instructions

Open a Monograph page in your signed-in Cloud Browser (default https://app.monograph.com) to work with architecture and engineering firm management with projects, staffing, budgets, time and billing.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.monograph.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 mentions the "signed-in" session, hinting that authentication is pre-handled, but says nothing about what happens when no browser session exists, whether calling it closes or replaces an existing page, or what the tool returns (navigation confirmation vs. page content). For a stateful browser-control tool with zero annotation coverage, that is a substantial gap.

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 the action and target first, which is efficient. The trailing enumeration of Monograph's business domain ("projects, staffing, budgets, time and billing") is marketing filler that does not help an agent invoke the tool correctly.

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 one-parameter navigation tool with no output schema and no annotations, the description covers what and where but leaves behavior around session state and return values unstated. No output schema exists to fill that gap, so the definition is adequate rather than complete.

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 url parameter is already described with its default, so the description adds essentially nothing new on parameters; it only restates the default URL. Baseline 3 applies since the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Open a Monograph page") plus the execution environment ("signed-in Cloud Browser"), which clearly separates it from siblings like monograph_click, monograph_read, and monograph_close. The trailing clause identifies the application domain, so an agent knows exactly what this tool does.

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?

No explicit when-to-use or when-not guidance, and no routing to alternatives such as monograph_guide or monograph_status. Usage is only implied by the word "Open" — an agent can infer this is the entry point for beginning browser work, but it is left to inference.

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