Skip to main content
Glama

contractor_foreman_close

Close the Contractor Foreman browser session to stop credit usage when work is complete. Use it to end an active session and halt ongoing charges.

Instructions

Close the Contractor Foreman browser session when the work is done, so credits stop running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses a genuinely non-obvious consequence: credits stop running once the session is closed, revealing that the session is a metered resource. It doesn't state failure behavior (e.g., closing when no session is open), whether the action is idempotent, or whether any in-progress state is lost, leaving some behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the action first and the rationale trailing, containing no filler. Every clause earns its place.

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 zero-parameter session-termination tool with no annotations and no output schema, the description covers what it does and why it matters cost-wise. Only the edge cases (no active session, state preservation) are unaddressed.

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 beyond what the empty schema already conveys. Baseline of 4 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 pairs a specific verb ("Close") with a specific resource ("the Contractor Foreman browser session"), which makes it clearly distinct from siblings like open, read, click, and type. It stops short of explicitly naming the complementary tool (contractor_foreman_open), but the intent is unambiguous.

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?

"when the work is done" gives a clear temporal trigger for invocation rather than leaving usage implicit. There are no explicit exclusions or pointers to alternatives (e.g., check status first, or keep the session open for follow-up work), which keeps it from a 5.

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