Skip to main content
Glama

Attify

Look up a vendor's verification

lookup_vendor
Read-onlyIdempotent

A vendor's published Attify verification: status (Claim confirmed · within 5.0 points when Attify is 95% sure the vendor's count overstates audited outcomes by at most the claim tolerance, the gap's upper 95% limit being within it; Claim not confirmed; Lapsed; or Revoked), audited rate against the vendor's own claimed rate with 95% intervals, the gap, evidence tier, provenance (connected, or witnessed with how many counted customers' data the vendor streamed and they reconciled), the contact-reason mix (support resolution), rank within its job type, period, standard version and the signed attestation. Give the profile slug, or a name to search. Rates compare only within one job type, and for support resolution next to the contact-reason mix.

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": "lookup_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the vendor's or product's name.
slugNoThe profile slug, e.g. "acme-ai-resolve-bot".
job_typeNoLimit to one job type: "support-resolution", "sales-meetings", "bookings".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description does add substantive interpretive context — what each status value means, including the statistical tolerance behind 'Claim confirmed' — which is real added value beyond annotations, but it says nothing about ambiguous names, multiple matches, or error behavior.

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

Conciseness2/5

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

The opening is a single sprawling run-on sentence dense with statistical jargon ('within 5.0 points', 'upper 95% limit') before the reader learns what the tool actually does. It is not front-loaded on purpose, and the guidance sentences are appended rather than structured.

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 must carry the return shape, and it does cover status semantics, audited vs claimed rate, gap, evidence tier, provenance, contact-reason mix, rank, period, standard version, and attestation. Missing only the resolution of ambiguous name searches and the handling of a name+slug combination, which keeps it from a 5.

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%, so all three parameters are documented in the schema itself, setting the baseline at 3. The description adds a little meaning for job_type ('rates compare only within one job type') and a slug usage example, but it does not clarify whether name is substring matching or how name and slug interact if both are supplied.

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 conveys that this returns a vendor's published Attify verification profile, and the field enumeration plus 'Give the profile slug, or a name to search' makes the action inferable. However, the purpose is buried under a long list of returned attributes rather than stated as a verb+resource up front, and no sibling (get_verdict, compare_subjects, get_evidence) is named to differentiate it.

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?

The only guidance is 'Give the profile slug, or a name to search' and the caution that rates compare only within one job type. There is no statement of when to prefer this over sibling lookup/verdict/compare tools, no note on which identifier to prefer, and no exclusions.

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