Skip to main content
Glama

Attify

Get a verdict

get_verdict
Read-onlyIdempotent

The answer first: one verdict sentence, then claimed, audited and the gap with 95% intervals, the evidence tier, provenance (connected, witnessed or uploaded; for witnessed data whether the customer reconciled it), judge validation, the drivers of the gap, the period, sample sizes and the data's scope. For a published vendor (by slug) or the public sample audit.

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

Input Schema

NameRequiredDescriptionDefault
vendorNoA published vendor's profile slug, e.g. "acme-ai-resolve-bot". Omit for the public sample audit (synthetic demo data, labelled as such).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds substantial behavioral context about what the payload contains — evidence tiers, provenance states (connected/witnessed/uploaded, including whether witnessed data was customer-reconciled), judge validation, gap drivers, period, and sample sizes. It does not cover failure behavior (e.g. unknown slug) or whether results are cached/live, which keeps it short of a 5.

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 content is dense with no filler, but it is delivered as one long run-on sentence enumerating payload fields, with the odd front-loading "The answer first". It would be clearer as a short purpose sentence followed by a structured list of what is returned.

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 explaining return values — and it does so thoroughly, naming the interval-bearing metrics, provenance, validation, drivers, and scope. What remains thin is the front-end: a crisp statement of purpose and any preconditions for a vendor to have a verdict.

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 the single parameter's semantics (slug format, omitted => synthetic public sample) are fully documented in the schema. The description's mention of "by slug" and "the public sample audit" restates rather than extends that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with "The answer first: one verdict sentence, then claimed, audited and the gap with 95% intervals...", which is a return-payload inventory rather than a direct statement of what the tool does. A reader can infer it returns a vendor's claimed-vs-audited verdict, but the subject of the verdict is never stated outright, and nothing distinguishes it from the sibling get_monthly_verdict.

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?

"For a published vendor (by slug) or the public sample audit" gives scope-based usage, implicitly telling the agent this works for published vendors or the demo sample. There is no explicit when-not, no prerequisite (e.g. whether the vendor must first be audited/connected), and no routing guidance versus get_monthly_verdict, get_evidence, or get_standard.

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