Skip to main content
Glama

Attify

Compare vendors

compare_subjects
Read-onlyIdempotent

Two to five published vendors of one job type side by side: audited against claimed with 95% intervals, the gap, evidence tier, provenance, period and, for support resolution, always each one's contact-reason mix. Vendors of different job types or standard versions are refused, and differences inside the intervals are not distinguishable.

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": {
      "vendors": "<vendors>"
    },
    "name": "compare_subjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorsYesProfile slugs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description adds real value on top: which inputs are refused, what dimensions are returned, and how to read overlapping intervals. It does not say anything about ordering of the returned vendors, error payload shape, or cost, but the safety and interpretation profile is well covered.

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?

Purpose and cardinality are front-loaded in the first clause, and every subsequent clause carries information (returned dimensions, refusal rules, interval caveat). The single dense sentence is harder to scan than a short bulleted structure would be, which keeps it below a 5.

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?

There is no output schema, so the description has to carry the return contract, and it does list the compared dimensions and the always-included contact-reason mix for support resolution. It omits result ordering, what a partial or refused request returns, and any note on how many rows to expect beyond the 2-5 input bound, leaving minor gaps for a comparison tool of this complexity.

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 schema already documents the 'vendors' array with minItems 2 and maxItems 5, so the baseline is 3. The description earns above baseline by qualifying what the slugs must denote: published vendors, all of one job type, on the same standard version, and it warns that violations are refused.

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?

The description names a specific verb and resource ('two to five published vendors of one job type side by side') and enumerates the comparison dimensions: audited vs claimed with 95% intervals, the gap, evidence tier, provenance, period, and contact-reason mix. 'Published vendors of one job type' also implicitly separates it from compare_my_agents, which operates on the caller's own agents.

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?

It states inclusion criteria (2-5 vendors, published, one job type, same standard version) and the refusal conditions for mismatched vendors, plus an interpretation rule that differences inside the intervals are not distinguishable. It does not point to a single-vendor alternative such as lookup_vendor when comparison is inappropriate, so it stops short of full routing guidance.

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