Skip to main content
Glama

Compare Provider

compare-provider
Read-onlyIdempotent

How JustLabs compares with another lab-testing provider (e.g. everlywell, testwell, quest, labcorp): a short verdict, side-by-side facts with sources, where each one is the better choice, FAQs and a link to the full comparison page. Product terms only.

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": {
      "provider": "<provider>"
    },
    "name": "compare-provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNo
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine beyond-annotation value by disclosing the shape of the response (verdict, sourced facts, FAQs, outbound link) and the 'product terms only' restriction. It stops short of saying what happens for an unrecognized provider or how the external link is qualified.

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?

A single front-loaded sentence that leads with the core action and then enumerates contents, with no filler. The list is dense but every clause corresponds to something the agent would otherwise have to guess.

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 two-parameter read-only tool with no output schema, the description explains what comes back well enough that the agent knows what to expect. The main residual gaps are locale behavior and unknown-provider handling, which are minor for this complexity level.

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 0%, so the description carries the burden; it does so partly by giving concrete provider examples (everlywell, testwell, quest, labcorp), which materially clarifies the required 'provider' string. The 'locale' parameter (en/es) is never mentioned in prose, so half the parameters get no added meaning.

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 concrete verb and resource (compares JustLabs with another provider) and enumerates the payload: verdict, side-by-side facts with sources, best-choice guidance, FAQs, and a link to the full page. This differentiates it in substance from a price-only comparison sibling, though it never names that sibling explicitly.

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?

'Product terms only' is a real scope exclusion that hints at when this tool is the wrong pick (e.g. for pricing), but there is no explicit 'use compare-prices instead' routing or statement of preconditions. Usage is implied rather than directed.

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