Skip to main content
Glama
Sign In

Red by Big Red Cloud

by io.github.BigRedCloud
OverviewDiscussionsAdmin

Get Red Help

brc_red_help
Read-only

Returns Big Red Cloud help and manual Big Red Cloud instructions for how-to questions, including how do I queries and tutorials. Covers topics including sales invoices, purchases, customers, suppliers, banking, VAT, reports and company setup. Searches Freshdesk, YouTube, BRC Edu, webinars and screenshots. Read-only and available without a connected company. UI guidance in returned resources is official reference material; RED does not change company setup.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "brc_red_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText after the red-help command, for example how do I add a sales invoice or add a customer manually.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description earns credit for added operational facts: it is available without a connected company and it does not modify company setup. The list of searched sources (Freshdesk, YouTube, BRC Edu, webinars, screenshots) also tells the agent to expect mixed-media results, though it slightly sits in tension with openWorldHint=false and says nothing about result limits or ranking.

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?

Purpose and scope are front-loaded in the first sentence, with topic coverage and sources following in supporting order. The closing 'UI guidance ... official reference material' clause is useful but worded densely and is the least essential sentence.

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 single-parameter, read-only retrieval tool with no output schema, the description covers what it searches, what topics, and the no-connection requirement — enough to call it correctly. The main omission is any indication of what a returned resource looks like (link, snippet, media).

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 schema already supplies an example query string, so the schema carries the parameter burden. The description only adds that queries are natural-language how-to phrasing, which is a marginal gain over the schema's own example.

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 ('Returns Big Red Cloud help and manual instructions') and scopes it to how-to/tutorial questions, which separates it from CRUD siblings in the brc_* family. It does not explicitly name the closest help siblings (brc_find_help_resources, brc_get_help_resource_details), so the disambiguation is implied rather than stated.

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?

Gives concrete triggering conditions: 'how-to questions', 'how do I queries', 'tutorials', plus topic scope (invoices, VAT, banking, reports, company setup). It also implies when not to use it ('RED does not change company setup'), but it never routes the agent to a specific alternative help tool for resource lookup vs. detail retrieval.

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

All Red by Big Red Cloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources