Skip to main content
Glama

Attify

The Attify Index

get_index
Read-onlyIdempotent

What AI agents achieve, by job type: the pooled audited share of the outcomes they claimed, with its 95% interval (each company a cluster), evidence tier, provenance mix, failure modes and monthly trend, from companies that contribute their anonymous data. Published for a job type only with enough contributing companies and none above half the claims. Names no company, vendor or agent. Give job_type for one job.

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_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoA past edition, YYYY-MM: as published, permanently. Omit for the latest.
job_typeNoOne job type: "support-resolution", "sales-meetings", "bookings".

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 establish this as a read-only, idempotent, closed-world lookup, so the bar is lower. The description still adds real behavior the annotations cannot: the publication threshold rule (only with enough contributing companies, and no single company above half the claims) and the anonymity guarantee ('Names no company, vendor or agent'). What it does not say is what the caller receives when a job type fails the threshold — an error, an empty result, or a suppressed flag.

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?

It is one dense paragraph but each clause earns its place: the return dimensions are worth listing because no output schema exists, and the publication rule is essential. The opening 'What AI agents achieve, by job type' is softer than the rest of the text, and the packed mid-sentence list of six returned fields is harder to scan than a short enumeration would be. Still, there is no filler.

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 correctly compensates by naming the result dimensions, and it explains the gating logic that determines whether a result exists at all. For a two-parameter, read-only aggregation tool this is close to sufficient; the remaining gap is the suppressed/threshold-not-met response shape and whether historical months can be 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%, with both month (YYYY-MM pattern, 'omit for the latest') and job_type (three enumerated values) fully documented in the schema itself. The description only restates the singular framing ('Give job_type for one job'), which is a useful scope constraint but adds little syntax or meaning beyond the schema. Baseline 3 applies when 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 names a specific resource (a pooled, audited outcome share by job type) and enumerates exactly what the metric carries: 95% interval with company-level clustering, evidence tier, provenance mix, failure modes, monthly trend. It is clearly a published index rather than a per-agent record, which separates it from get_agent_outcomes. It stops short of naming that sibling explicitly, so the differentiation is inferential rather than stated.

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?

The closing line 'Give job_type for one job' tells the agent how to invoke it for a single job type, and the schema notes that omitting month yields the latest edition. There is no explicit statement of when to use this versus get_agent_outcomes, get_monthly_verdict, or get_verdict, so the agent must infer the choice from the pooling angle alone.

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