Skip to main content
Glama

accelo_guide

Get guidance on Accelo screens, sign-in, and workflows for tickets, projects, time, and quotes; call it first to start tasks correctly.

Instructions

How to work in Accelo (manage tickets, projects, time and quotes): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Accelo, in your words.

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?

No annotations are supplied, so the description carries the full burden. It does disclose the content of the response (screens plus a sign-in link) and implies no prerequisites by telling the agent to call it first, but it says nothing about authentication state, output format, or whether the guide changes per task.

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 no filler, and the coverage scope (tickets, projects, time, quotes) is packed into a parenthetical rather than a rambling list. The critical instruction, "Call this first," is placed last where it lands as the takeaway rather than being buried.

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, read-only orientation tool with no output schema, the description covers purpose, call ordering, and a rough sketch of the return content. Only the shape of the returned guide is left underspecified, which is a minor gap at this complexity.

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?

The single optional `task` parameter is fully documented in the schema ("What you want done in Accelo, in your words"), and the description adds no further meaning about how to phrase it or how it shapes the returned guidance. With 100% schema coverage, the baseline of 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 identifies this as a guide/orientation tool covering Accelo's screens and sign-in link for tickets, projects, time and quotes, which clearly separates it from the action-oriented siblings (accelo_click, accelo_open, accelo_read, accelo_type). The verb is descriptive rather than precise, but an agent can tell this is the documentation/onboarding entry point rather than an operation.

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

Usage Guidelines4/5

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

"Call this first" is explicit ordering guidance that tells the agent when this tool precedes all others, which is exactly the sequencing decision an agent needs. It stops short of naming when-not-to-use or naming a specific alternative, but the implied contrast with the sibling action tools is strong enough to act on.

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