Skip to main content
Glama

provision_guide

Use this first-call guide to navigate Provision screens, sign-in, bid documents, scope gaps, packages, contract risks, and review checklists.

Instructions

How to work in Provision (pre-construction bid documents, scope gaps, scope packages, contract risks and review checklists): 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": "provision_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Provision, 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?

With no annotations, the description carries the full burden: it implies an informational, non-mutating response (screens, sign-in link, how-to concepts) but never confirms it has no side effects. It also does not say what form the guidance takes or whether it returns a URL, steps, or screen list.

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?

One compact sentence covering scope plus a short imperative ('Call this first'), front-loaded with the resource. The parenthetical topic list is dense but each item is informative.

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-parameter orientation tool with no output schema, the description establishes scope and call ordering but omits what the caller receives and how to act on it, which is the main thing an agent needs from a guide entry point.

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 'task' parameter is already fully documented in the schema at 100% coverage, and the description adds no constraints, formatting hints, or examples for it. Baseline applies because 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 names the domain (pre-construction bid documents, scope gaps, scope packages, contract risks, review checklists) and the concrete outputs (screens, sign-in link), so it reads as an orientation/help entry point rather than an action tool. It is distinguishable from the provision_* action siblings, though the leading 'How to work in Provision' phrasing is descriptive rather than a crisp verb+resource statement.

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' gives explicit ordering guidance that routes the agent ahead of the action siblings. It does not state when this tool is unnecessary or what an agent should do with the result afterward, so it falls 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.