Skip to main content
Glama

breely_guide

Get guidance on navigating Breely for bookings, availability, forms, invoices and client reports, including the sign-in link, before calling other tools.

Instructions

How to work in Breely (bookings, availability, forms, invoices and client reports): 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": "breely_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Breely, 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 burden. It discloses the content scope (screens, sign-in link) which usefully signals the agent will get orientation material, but it never states the return form — text, link, screen list — or that this is a non-mutating, safe lookup with no side effects.

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 sentences, front-loaded with the coverage area followed by the action directive; no filler. The parenthetical domain list is dense and useful, though the fragment 'its screens and the sign-in link' reads awkwardly and could be stated more cleanly.

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 single optional-parameter guide tool with no output schema and no annotations, the description covers what topics are addressed but not what an agent receives back or how to use the result. It is adequate to select the tool but leaves a meaningful gap about the response.

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 'task' parameter is already documented in the schema, so the baseline applies. The description adds nothing about how the free-text task influences the returned guidance, leaving the parameter's effect unexplained beyond the schema wording.

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?

Names a specific resource (Breely orientation/how-to guide) and enumerates the covered domains — bookings, availability, forms, invoices, client reports — plus screens and the sign-in link. It is clearly distinguishable from the sibling UI-action tools (click, open, close, read, type, status), though the phrasing 'How to work in' is slightly passive about what the tool actually returns.

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 an explicit, unambiguous ordering instruction that tells the agent when to reach for this tool relative to everything else. It stops short of naming any exclusion or stating what to do after the guide is consumed, so it is strong context without full when/when-not coverage.

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