Skip to main content
Glama

extrabat_guide

Get step-by-step guidance on working in Extrabat, including its screens and the sign-in link. Call this first to orient users before managing customers, quotes, site visits, or after-sales.

Instructions

How to work in Extrabat (customers, quotes, site visits and after-sales): 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": "extrabat_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Extrabat, 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 disclosure burden alone. It implies a non-mutating information tool by describing it as 'how to work in Extrabat', but it never states that it changes nothing, nor does it describe what the response looks like — relevant since there is no output schema to fall back on.

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 compact sentences with the scope listed parenthetically and the call-first instruction front-loaded at the end for emphasis. The first sentence is a fragment, which costs a little readability, but no sentence is wasted.

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 simple one-optional-parameter orientation tool with no output schema, the description covers the domain scope and the invocation ordering. The main residual gap is a brief statement of the form of what comes back (instructions, links, screen names), which the description only hints at.

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?

There is a single optional parameter with 100% schema coverage, so the schema already explains it as 'what you want done in Extrabat, in your words'. The description adds nothing about how to phrase that task or how it affects the returned guidance, so 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 names the resource (Extrabat guidance covering customers, quotes, site visits, after-sales, screens and the sign-in link), which is specific enough for an agent to understand it returns orientation material rather than performing an action. It does not use a clear verb like 'returns' or 'explains', leaving the output nature slightly implicit, and it draws no explicit contrast with the sibling action tools (click, open, type, read, close).

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 sequencing instruction that tells the agent to invoke it before the extrabat_* action tools, which is real, actionable guidance. There are no stated exclusions or conditions for skipping it, so it stops short of 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.