Skip to main content
Glama

contractor_foreman_read

Reads the active Contractor Foreman page, returning its text and numbered buttons, links, and fields so an AI agent can inspect and act on page elements.

Instructions

Read the current Contractor Foreman page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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 still communicates a read operation against current page state and discloses the principal content exposed. It does not clarify snapshot versus live behavior, output limits, any page-open requirement, or how element numbers are subsequently used.

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 compact sentence front-loads the operation and target, then efficiently lists the exposed content. There is no filler or redundancy.

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 simple one-parameter read tool, the description and schema provide enough to make a basic call and understand the broad result despite the absence of an output schema. Any page-open prerequisite and the relationship between numbered elements and the element parameter remain unclear.

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 sole optional element parameter is fully described in the schema, so the baseline of 3 applies. The description’s mention of numbered controls adds some context, but it never explicitly states that element accepts one of those numbers or how scoping changes the result.

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 and resource—“Read the current Contractor Foreman page”—and identifies the content as text plus numbered buttons, links, and fields. It clearly conveys inspection rather than interaction, but does not explicitly differentiate the tool from siblings such as status or guide.

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?

The wording implies use for inspecting the current page and discovering numbered controls before further interaction. It provides no explicit prerequisites, when-not guidance, or routing to alternatives.

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