Skip to main content
Glama

Attify

Compare my AI agents

compare_my_agents
Read-onlyIdempotent

Your company's AI agents of one job type side by side for a month: each one's audited share of claims with its 95% interval, cost per audited outcome and main failure mode, and the pooled rate of other contributing companies where it can be shown (anonymous, each company a cluster). Differences inside the intervals are not distinguishable. Side by side comes with the Business plan. Needs sign-in to Attify; reads only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_my_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoYYYY-MM; omit for the latest.
job_typeNoe.g. "support-resolution". Omit when all your agents do one job.

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, non-destructive, and closed-world behavior, so the bar is lower. The description still adds real context beyond them: plan gating (Business plan), an authentication requirement, the anonymized cross-company pooling ('each company a cluster'), and the interpretive caveat that differences inside the intervals are not distinguishable. It does not describe result ordering or size limits, but the behavioral picture is substantially enriched.

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?

The content is front-loaded in one dense sentence that states what is compared and what each row contains, followed by short sentences on the statistical caveat, plan gating, and auth. Every sentence carries information, though the opening sentence packs several concepts and is heavier than ideal.

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?

There is no output schema, and the description compensates well by enumerating the returned fields: audited share of claims with a 95% interval, cost per audited outcome, main failure mode, and pooled cross-company rate. Combined with the plan, auth, and interpretability notes, an agent has everything needed to decide whether to call it and how to read the result.

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% and both parameters are documented there (month as YYYY-MM with omit-for-latest, job_type with an example and an omit-when-single-job rule). The description only echoes the month and single-job-type framing, adding no format or edge-case detail beyond the schema. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

The description uses a specific verb+resource: comparing the caller's own AI agents of one job type side by side over a one-month window. It clearly names the scope ('your company's AI agents', 'one job type', 'a month'), which separates it from broader vendor/term/badge siblings without needing to name them. It stops short of explicitly disambiguating against lookalike comparison or outcome-listing tools.

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 by the description (compare agents of a single job type for a given month) and the prerequisites are stated: it requires the Business plan and an Attify sign-in. However, there is no explicit guidance on when to prefer this over, say, retrieving raw agent outcomes or another comparison tool, so the agent has to infer the choice.

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