Skip to main content
Glama

Attify

Explain where data came from

explain_provenance
Read-onlyIdempotent

What each provenance level means and what it can support: connected (Attify pulled every record from the customer's own system), witnessed (the vendor's agent streamed each interaction to Attify as it happened, signed and timestamped; it counts toward a verification only once the customer consented and reconciled it each month) and uploaded (a file, self-reported, never a verification). Also how an agent on its own platform sends witnessed data: the Ingest API, the Python and TypeScript SDKs, or OpenTelemetry, with the endpoints, schema and docs. Give a level to explain one.

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

Input Schema

NameRequiredDescriptionDefault
levelNoOne level; omit for all three.

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, closed-world and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: it says what each level does and does not support (uploaded is 'never a verification'; witnessed counts only after consent and monthly reconciliation), and it discloses extra content — Ingest API, Python/TypeScript SDKs, OpenTelemetry, endpoints, schema and docs.

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 front-loaded with the three level definitions before the ingestion detail, and every clause carries information. The parenthetical for 'witnessed' is a long run-on, and the ingestion-material sentence is dense, but nothing is padding.

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 and one optional parameter, the description must carry the content burden, and it does — it explains what is returned (level meanings, what they support, ingestion methods with endpoints, schema and docs). Only the shape of the returned text when a single level is chosen is left implicit.

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?

Coverage is 100% on a single optional enum parameter, so the schema already carries the baseline. The description does not explain what selecting a single level changes about the response (shorter vs. full answer), adding little meaning beyond the enum itself, so baseline 3 applies.

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: it explains what each provenance level (connected, witnessed, uploaded) means and what it can support, and enumerates the ingestion channels it also documents. An agent can tell this is the provenance-explanation tool, though it never explicitly separates itself from neighbors like explain_check or define_term.

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 sentence 'Give a level to explain one' implies how to narrow the call to a single level (versus the schema's 'omit for all three'). Usage is implied rather than framed with when-to-use or when-not-to-use conditions, and no alternative tools are named.

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