Skip to main content
Glama

contractor_foreman_status

Check whether your Cotlet.dev account, available credits, and Contractor Foreman connection are ready before running construction management tasks.

Instructions

Check that your Cotlet.dev account and Contractor Foreman are ready: account, credits and Contractor Foreman connection.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. "Check" implies a read-only probe, but the description does not say whether it contacts external services, how long it takes, what happens when the account or connection is not ready, or what the result looks like. Only the scope of the inspection (account, credits, connection) is disclosed.

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?

A single front-loaded sentence with no filler, and the enumerated checks are appended compactly. Slightly clipped phrasing ("account" appears both as the readiness subject and again in the list) keeps it from being perfectly clean, but nothing is wasted.

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 zero-argument diagnostic with no output schema and no annotations, the description tells the agent what is examined but not what a result means — no indication of pass/fail shape, error signaling, or remediation. An agent can decide to call it, but cannot fully anticipate or interpret its response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The colon list is a summary of what is inspected rather than an input mapping, which is appropriate here.

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 uses a specific verb ("Check") and names the concrete things being verified: the Cotlet.dev account, credits, and the Contractor Foreman connection. That is far more than a restatement of the name. It does not, however, say how it differs from siblings like contractor_foreman_guide or contractor_foreman_read, though none of those names suggest an obvious overlap with a readiness probe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the framing "Check that ... are ready" suggests a pre-flight/verification step before other Contractor Foreman operations. It never states explicitly when to call it, whether it should precede every action, or what to do if it reports a problem.

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