Skip to main content
Glama

accelo_open

Opens an Accelo page in your signed-in Cloud Browser so you can manage tickets, projects, time, and quotes.

Instructions

Open a Accelo page in your signed-in Cloud Browser (default https://accelo.com) to work with manage tickets, projects, time and quotes.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://accelo.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/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 does disclose the key behavioral trait that the page opens in a signed-in Cloud Browser session (i.e., authenticated context), which is useful. It says nothing about whether the call returns page content, whether it navigates away from the current page, or what side effects occur.

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 sentence with the action and default front-loaded, so it is easy to scan. The closing list of Accelo features is slightly redundant and the phrasing 'to work with manage' is awkward, but nothing is seriously bloated.

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?

The tool is simple (one optional param, no output schema, no annotations), and the description covers what it does and the default target. However, for an entry-point tool it omits what an agent should expect afterwards and how it relates to accelo_read/accelo_click, leaving a meaningful gap.

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?

Only one optional parameter, and schema coverage is 100%, so the schema already documents the url field and its default. The description repeats the same default rather than adding new meaning (e.g., accepted URL forms or relative paths). 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?

States a specific verb and resource: open an Accelo page in the signed-in Cloud Browser, with the default URL given. This distinguishes it from siblings like accelo_read and accelo_click, though the trailing clause ('to work with manage tickets, projects, time and quotes') is grammatically garbled and adds noise rather than precision.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to choose this over alternates such as accelo_read or accelo_click, nor any prerequisites or exclusions. An agent must infer that this is the navigation/entry step before other browser tools.

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