Skip to main content
Glama

Attify

Monthly verdict

get_monthly_verdict
Read-onlyIdempotent

Your company's verdict for a month on each AI agent it pays for, as emailed on the 1st: the verdict sentence, the audited share of the vendor's claimed outcomes with its 95% interval, the cost per audited outcome, the change since the month before, the evidence tier, provenance and standard version. Last month by default. For companies that buy AI agents. 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_monthly_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoYYYY-MM; omit for the latest.

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, non-destructive, and closed-world, so "reads only" merely restates them. The description adds genuine context beyond the annotations: the Attify sign-in requirement and the default-period rule (last month when month is omitted). It does not cover failure modes, whether a not-yet-published month errors, or rate/latency behavior.

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 is front-loaded in the first clause, followed by the payload enumeration, then the operational notes on scope, auth, and default. The field list is dense but each item tells the agent what a result contains when no output schema exists. No filler sentences.

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 carries the burden of describing return values, and it does so field by field. Auth and default-period behavior are disclosed. What is missing is the relationship to the non-monthly verdict tool and any statement about what happens when no verdict exists for the requested month.

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% and the single month parameter already documents the YYYY-MM pattern and "omit for the latest", so the baseline is 3. The description's "Last month by default" adds a useful hint but sits slightly in tension with the schema's "omit for the latest," leaving a small ambiguity about whether the default is the previous calendar month or the most recent available.

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 specific verb and resource ("monthly verdict ... on each AI agent it pays for") and enumerates exactly what the payload contains: verdict sentence, audited share with 95% interval, cost per audited outcome, month-over-month change, evidence tier, provenance, standard version. That is far more specific than the title. It stops short of naming a sibling such as get_verdict, so an agent must infer that this is the monthly/periodic variant rather than the current one.

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?

Implied usage is clear from "as emailed on the 1st" and "For companies that buy AI agents", and "Last month by default" gives the default period behavior. However, there is no explicit when-to-use versus when-not, and no pointer to get_verdict or compare_my_agents for other reporting needs, so the agent has to reason about routing itself.

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