Skip to main content
Glama

workquote_guide

Explains how to navigate WorkQuote to manage estimates, jobs, and invoices and find the sign-in link; call it first for task guidance.

Instructions

How to work in WorkQuote (manage estimates, jobs and invoices): 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": "workquote_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in WorkQuote, 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 must carry the behavioral burden. It discloses the subject matter (screens, sign-in link) but not the return shape, whether the call is side-effect free, or how the task parameter influences the response. The "guide" framing implies an informational read, but that is inference rather than disclosure.

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 the scope statement first and the call-to-action last, so the important instruction lands where an agent will read it. The parenthetical "its screens and the sign-in link" is slightly adjectival and could be folded into a clearer statement of what is returned.

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 structurally simple — one optional string parameter, no output schema, no nested objects — so the description need not explain return values in detail. However, an agent still cannot tell what calling it yields (a text guide? a link?) or whether supplying task changes that, which matters because the whole point of the tool is to steer subsequent calls.

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%, so the schema already documents the single "task" property in full. The description adds nothing about it — not that it is optional, nor what happens when it is omitted or how it shapes the returned guidance. Baseline 3 applies when the schema does all the work.

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 states the resource ("How to work in WorkQuote") and enumerates its coverage: estimates, jobs, invoices, screens, and the sign-in link. It also differentiates from siblings with the sequencing cue "Call this first." It stops short of a crisp verb+"returns a guidance document" phrasing, leaving the exact nature of the output implicit.

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 an agent to invoke this before the other workquote_* tools. There are no when-not conditions or named alternatives, but for an entry-point guide tool that single directive covers the primary routing decision.

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