Skip to main content
Glama

ontraccr_guide

Explains how to work in Ontraccr, covering sign-in, screens for crew time cards, form approvals, field shifts, project budgets and board cards. Call it first for step-by-step guidance.

Instructions

How to work in Ontraccr (crew time cards, form approvals, field shifts, project budgets and board cards): 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": "ontraccr_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Ontraccr, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It hints at content ('its screens and the sign-in link') but says nothing about the return format, whether output is static or tailored, whether the task parameter alters the response, or any auth/rate considerations. The agent knows this is orientation rather than an action, but not what it will actually receive.

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 sentences, scope front-loaded, with an imperative 'Call this first' placed at the end where it is most salient. No redundant restatement of the name, though 'its screens and the sign-in link' is a compressed phrase that reads slightly vaguely.

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 optional-parameter guide tool with no output schema, the description is adequate: it establishes domain scope and call ordering. It leaves open what the returned guidance looks like and how the free-text task input shapes it, which are the remaining gaps an agent would want closed.

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% and the single task parameter is fully documented in the schema as 'What you want done in Ontraccr, in your words.' The description never mentions the task parameter and adds no syntax or formatting guidance beyond the schema, so the baseline of 3 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 names the resource (Ontraccr) and specifies what the tool gives back: an orientation guide covering screens, the sign-in link, and named functional areas (crew time cards, form approvals, field shifts, project budgets, board cards). 'How to work in' is slightly fuzzy as a verb, but the enumerated coverage makes the tool's role distinct from the operational siblings (click, open, type, 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?

'Call this first' is an explicit, unambiguous usage directive that tells the agent exactly when to reach for this tool relative to the other ontraccr_* operations. It stops short of stating when this tool is unnecessary (e.g., once orientation is complete), but for an onboarding/guide tool the ordering guidance is the key signal.

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