Skip to main content
Glama

studio_ninja_open

Opens a Studio Ninja page in your signed-in Cloud Browser so you can manage leads, jobs, contracts, invoices, and overdue payments.

Instructions

Open a Studio Ninja page in your signed-in Cloud Browser (default https://studio-ninja.com) to work with leads, jobs, contracts, invoices and overdue payments.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://studio-ninja.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight; it does disclose that the browser is 'signed-in' (auth state) and that the domain defaults to https://studio-ninja.com. It does not say whether navigation replaces the current page, what happens on an invalid URL, or whether it returns page content, leaving meaningful gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the action, names the target domain, and lists the work domains in one compact clause. No filler or redundancy.

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 one-optional-parameter navigation tool with no output schema, the description covers the action, default target, and session context adequately. Only minor gaps remain, such as whether the opened page's content is returned or must be read with a sibling tool.

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 optional url parameter is fully documented in the schema, including the default. The description merely restates the same default, adding no format hints (absolute vs relative paths) beyond what the schema already 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 uses a specific verb and resource ('Open a Studio Ninja page') and scopes the target domain, so an agent can distinguish it from siblings like studio_ninja_read or studio_ninja_click. It stops short of explicitly contrasting itself with those siblings, keeping it a clear-but-not-differentiating 4.

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 purpose clause ('to work with leads, jobs, contracts, invoices and overdue payments') implies when this tool is appropriate, giving useful domain context. However, there is no explicit guidance on when to choose this over studio_ninja_read or studio_ninja_guide, and no stated preconditions or exclusions.

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