Skip to main content
Glama

Search the Jobsite product guide

lookup_jobsite_docs
Read-onlyIdempotent

Look up how Jobsite (this product) works — features, UI navigation, terminology, account / billing, worker-side experience, what counts as a 'group' vs 'crew', etc. Use this for any 'how do I…' / 'where do I find…' / 'what does X mean in Jobsite' question. Returns matching sections from the curated product guide. NOT for OSHA / regulatory questions (use search_law_corpus) and NOT for a company's own records (its workers, certificates, jobs). If a returned section is flagged todo:true, the topic is in scope but not yet documented — say so rather than inventing an answer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "lookup_jobsite_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax sections to return. Defaults to 4, cap 8.
queryYesNatural-language query, e.g. 'how do I add a worker', 'difference between groups and crews', 'where do I see expiring certs'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety needs no restating. The description instead discloses non-obvious behavior the annotations cannot carry: results come from a curated guide, and a returned section with todo:true means the topic is in scope but unwritten, with an explicit instruction to report that rather than invent an answer. That is exactly the kind of failure-mode guidance that changes agent behavior.

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?

Front-loaded with purpose, then usage triggers, then exclusions, then the todo:true caveat — a sensible priority order with no filler sentences. It is mildly dense as a single run-on block, and the parenthetical '(this product)' plus the 'etc.' tail are minor slack.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter search tool with no output schema, the description covers purpose, in-scope topics, out-of-scope topics with a named alternative, the shape of the return value (matching sections), and what to do on an undocumented hit. Nothing needed to invoke it correctly is missing.

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 coverage is 100% and both parameters are already documented in the schema, including the default (4) and cap (8) for limit and example query strings. The description adds nothing about parameter usage beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Look up how Jobsite works' from the curated product guide) and enumerates the topic space covered (features, UI navigation, terminology, billing, worker-side experience, group vs crew). It explicitly names what it is not — regulatory search and company records — so an agent can separate it from search_law_corpus and search_articles without opening a schema.

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

Usage Guidelines5/5

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

Gives concrete trigger phrasing ('how do I…', 'where do I find…', 'what does X mean in Jobsite') and states two explicit exclusions with the alternative tool named for one of them (search_law_corpus). This is the when-to-use / when-not-to-use / alternative pattern in full.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources