Skip to main content
Glama

contractor_foreman_guide

Access guidance for navigating Contractor Foreman, signing in, and managing projects, estimates, and invoices; call this first to learn how to perform account tasks.

Instructions

How to work in Contractor Foreman (manage projects, estimates 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": "contractor_foreman_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Contractor Foreman, 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 full disclosure burden. It scopes the content (screens and sign-in link) but never states that the tool is read-only/non-mutating, what form the guidance returns in, or how comprehensive it is. Useful scope, but a meaningful gap for a tool with zero annotation coverage.

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 resource, its contents, and the call-ordering directive front-loaded and no filler. The parenthetical list of domains (projects, estimates, invoices) is mildly redundant with 'screens' but does usefully bound scope.

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 one-optional-parameter, no-output-schema guide tool the description is close to sufficient, but it leaves open whether the 'task' argument is needed for a useful response and what the returned guidance looks like. Adding a single sentence on those points would close the gap.

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 description coverage is 100%, with the single 'task' parameter already documented as 'What you want done in Contractor Foreman, in your words.' The description adds no guidance on how to phrase that value, whether it is optional, or how it shapes the returned guidance, so it sits at the baseline.

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 resource and its content: an orientation guide to Contractor Foreman covering 'its screens and the sign-in link.' The verb is implicit ('How to work in...'), which is slightly softer than a concrete action verb, but an agent can tell this is an onboarding/knowledge tool rather than one of the action siblings like click, type, or read.

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?

Provides an explicit ordering rule with 'Call this first,' which is exactly the routing signal an agent needs before using contractor_foreman_open, click, or type. It does not name when-not-to-use or describe how it relates to each sibling, but the sequencing directive covers the main decision.

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