Skip to main content
Glama

Compare StaffBots with a named competitor

compare_to
Read-onlyIdempotent

Return the published comparison page for a competitor already on staffbots.ai (Onfleet, DailyDSP, DSP Workplace, Virtual Dispatcher, offshore VA agencies, AI receptionist tools, or an in-house dispatcher). The excerpt is the page text. Do not add claims.

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": {
      "competitor": "<competitor>"
    },
    "name": "compare_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitorYesCompetitor name or slug, for example onfleet or dailydsp.

Output Schema

NameRequiredDescriptionDefault
urlNo
errorNo
titleNo
excerptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so safety is covered. The description adds real behavioral context beyond that: it discloses the return shape ('The excerpt is the page text') and imposes a content constraint ('Do not add claims') that tells the agent to relay the text verbatim rather than embellish.

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?

Three short sentences, front-loaded with the action and scope, with the constraint last. Minor redundancy between 'Return the published comparison page' and 'The excerpt is the page text,' but nothing wasteful.

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?

An output schema exists, so return values need no explanation, and the single required parameter is fully documented. The description covers scope, accepted values, and the no-added-claims constraint, leaving little an agent would need to guess.

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?

Schema coverage is 100% and the single parameter already has an example, so the baseline is 3. The description earns a bump by enumerating the accepted competitor set (Onfleet, DailyDSP, DSP Workplace, Virtual Dispatcher, offshore VA agencies, AI receptionist tools, in-house dispatcher), which is not encoded as an enum in the schema.

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?

States a specific verb and resource: 'Return the published comparison page for a competitor already on staffbots.ai,' and enumerates the competitor categories covered. It does not explicitly differentiate itself from the overlapping sibling compare_vs_offshore_va, so an agent must infer that this is the general form.

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 implied rather than stated: the page must already exist on staffbots.ai, which usefully bounds when the call will succeed. There is no explicit when-not guidance and no alternative tool is named, even though compare_vs_offshore_va is an obvious overlapping sibling.

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