Skip to main content
Glama

Attify

Where my AI agents fail

get_agent_outcomes
Read-onlyIdempotent

One month of your company's AI agents, answer first: for each agent the verdict sentence, claimed against audited outcomes with the 95% interval, what the month cost, the cost per audited outcome against the price per claimed one, and where it fails: each failure mode's share of the claims, with suggestions for your own deployment and redacted examples, quoted as customer text. For companies that buy AI agents; what a plan does not include says so. 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": "get_agent_outcomes"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoOne agent: its name or id. Omit for every agent.
monthNoYYYY-MM; omit for the latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful operational context, namely that sign-in to Attify is required and that examples are redacted customer text, but it omits details like data freshness, rate limits, and what happens when no data exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope and return contents are front-loaded, but the first sentence is a dense run-on that is difficult to parse. The information is relevant, yet it would benefit from bulleted or sentence-separated structure instead of comma and semicolon chains.

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?

With no output schema, the description does the important work of enumerating what the report returns: verdicts, intervals, costs, cost ratios, failure modes, suggestions, and redacted examples. It also discloses sign-in requirements and caveats about plan coverage, leaving only minor gaps around ordering and pagination.

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 coverage is 100%, with both parameters fully described in the input schema. The description confirms the scope ('one month', 'for each agent') but adds no syntax or behavioral meaning beyond what the schema already provides.

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 names the resource precisely: one month of the company's AI agents, with per-agent verdicts, audited outcomes, cost comparisons, and failure-mode breakdowns. It is clearly a reporting tool, not a generic agent lookup, though it does not explicitly differentiate itself from siblings such as get_monthly_verdict or compare_my_agents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the audience ('For companies that buy AI agents') but gives no explicit when-to-use guidance or when-not-to-use conditions. It never names an alternative tool or explains how to choose between this and related verdict or comparison tools.

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