Skip to main content
Glama
Sign In

Housecall Pro MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Go to a page

cotlet_browser_navigate
Read-only

Opens url in the current tab, or goes history back or forward. Answers the page after it: the elements and text in view, with the same numbers.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA public http or https address, e.g. https://example.com.
dialogNoHow to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
historyNoInstead of `url`.
dialog_textNoText for a prompt dialog this step opens; implies accept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true, idempotentHint=false), and the description adds behavior the annotations do not: that the step returns the resulting page state (elements and text in view). It omits whether navigation blocks on load, what happens on timeout or failed load, and what the 'same numbers' refer to, leaving some behavioral gaps.

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?

Two short sentences with the primary action front-loaded and no filler. The closing clause 'with the same numbers' is cryptic and costs clarity rather than words, which keeps it just below top marks.

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?

With no output schema, the description does carry the burden of explaining the return value, and it does so only vaguely ('the elements and text in view, with the same numbers') without defining the numbering scheme or error behavior. For an open-world navigation tool that can trigger native dialogs, more on failure modes and load semantics would be needed for full completeness.

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%, so `url`, `dialog`, `history`, and `dialog_text` are already fully documented, including enum values and dialog defaults. The description restates only `url` and `history` and adds nothing about `dialog`/`dialog_text` semantics, so it does not exceed the baseline.

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 resource ('Opens `url` in the current tab') plus the alternate mode ('goes `history` back or forward'), which is clearly navigation rather than the sibling `cotlet_browser_open`. The 'current tab' phrasing implicitly separates it from opening a new browser context, but no sibling is named explicitly, so an agent must infer the distinction.

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 implied by the mechanics: supply `url` to navigate, `history` to move within the session. There is no explicit guidance on when to prefer `cotlet_browser_open` (new tab/session) versus this tool, nor when to follow a navigation with `cotlet_browser_read` instead of relying on the returned snapshot.

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

All Housecall Pro MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources