Skip to main content
Glama

ontraccr_open

Open an Ontraccr page in your signed-in Cloud Browser to manage crew time cards, form approvals, field shifts, project budgets, and board cards.

Instructions

Open a Ontraccr page in your signed-in Cloud Browser (default https://app.ontraccr.com/login) to work with crew time cards, form approvals, field shifts, project budgets and board cards.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.ontraccr.com/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the browser is signed-in (authentication is already handled), which is valuable behavioral context. It is silent on whether the page opens in a new or existing tab, what happens on an invalid/unreachable URL, and whether the response includes page content — material gaps 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?

A single front-loaded sentence with the action and default URL leading, followed by the supported work areas. The area list is somewhat padded but does inform which pages are worth opening, so nothing is seriously wasted.

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 low-complexity navigation tool with no output schema and one fully documented parameter, the description covers purpose, auth context and default URL. It stops short of describing post-open behavior or failure modes, which an agent would need to chain this correctly with ontraccr_read and ontraccr_click.

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?

There is only one optional parameter and schema description coverage is 100%, so the schema already states the default URL and the description merely repeats it. The list of app areas does add a hint that deep links to specific Ontraccr sections are valid targets, but no format or path guidance is given.

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 uses a specific verb plus resource ('Open a Ontraccr page in your signed-in Cloud Browser') and gives the default target URL, which clearly separates it from siblings like ontraccr_click, ontraccr_read and ontraccr_close. It does not name any sibling explicitly, but the action is unambiguous enough to select on.

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 intended use is only implied: the listed work areas (time cards, form approvals, shifts, budgets, board cards) suggest 'navigate here first, then use ontraccr_read/ontraccr_click'. There is no explicit when-to-use statement, no mention of ontraccr_guide or ontraccr_status as alternatives, and no guidance on whether this is needed before every other call.

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