Skip to main content
Glama

SCRIPTMASTERLABS — Provider Trust + CANON

Compare Providers

compare_providers
Read-onlyIdempotent

Compare 2-5 providers side by side using live evidence gathered the same way verify_provider gathers it — identity, payment-readiness, and status evidence for each target, returned as a separate envelope per provider. No composite score is computed and no winner is declared; unknown evidence stays unknown for every target. Free, read-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": {
      "targets": "<targets>"
    },
    "name": "compare_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYesTwo to five public HTTPS provider, source, MCP, A2A, or API URLs to compare; each is checked through the same live evidence path and returned in its own envelope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / targets / description
      Added value: +"Two to five public HTTPS provider, source, MCP, A2A, or API URLs to compare; each is checked through the same live evidence path and returned in its own envelope."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, yet the description adds real outcome semantics: no composite score, no winner, unknown evidence preserved as unknown for each target, and one envelope per provider. 'Free' also discloses cost, which no annotation conveys.

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 the verb and the comparison scope, and the non-goals (no score, no winner) follow immediately. The trailing 'Free, read-only' is slightly redundant with readOnlyHint, though 'Free' adds new cost information not present in annotations.

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?

With no output schema and a single-parameter input, the description carries the burden of explaining return shape and does so: separate envelopes per provider containing identity, payment-readiness, and status evidence. Combined with annotations covering safety, 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 description coverage is 100%, so the single targets parameter is already fully documented including the 2-5 bounds. The description restates that range and adds only a light note that each URL is checked through the same live evidence path, so it does not meaningfully extend parameter meaning.

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 (compare) and resource (providers), with a bounded scope of 2-5 targets. It explicitly distinguishes itself from verify_provider by framing the evidence path as the same one verify_provider uses, so an agent understands this is the multi-target variant.

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?

The 2-5 target range and the reference to verify_provider's evidence path imply the selection rule: use this when comparing several providers rather than verifying one. It stops short of an explicit exclusion sentence such as 'for a single provider use verify_provider instead,' leaving that inference to the agent.

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