Skip to main content
Glama

Attify

Ingest health

get_ingest_health
Read-onlyIdempotent

Health of your deployments that send witnessed data (the Ingest API, an SDK, OpenTelemetry, or read from your own agent platform account): healthy, degraded or no data and why, events and interactions in the scoring period, late interactions (never scored as witnessed), sequence gaps and breaks, the signed share, the last event, volume by month, and each customer's consent and reconciliation. 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_ingest_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
deploymentNoOne deployment: its id or name.

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds substantive behavior beyond them: it requires sign-in to Attify, it reports one of three states (healthy, degraded, no data) with reasons, and it clarifies a semantic rule that late interactions are never scored as witnessed. Return content is enumerated in detail, which matters since there is no output schema.

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?

Front-loaded correctly with the core noun phrase 'Health of your deployments', and every clause carries information about a distinct reported item. It is, however, a single long run-on sentence with a laundry list that would be easier to scan if the enumerated outputs were broken out or trimmed.

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 bears full responsibility for explaining return values, and it does so thoroughly (states and reasons, scoring-period counts, sequence gaps, signed share, last event, monthly volume, consent and reconciliation). Auth requirements are stated. Only minor gaps remain, such as behavior when no deployments exist or how the single-deployment filter interacts with the aggregate view.

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 optional parameter is fully described in the schema as a deployment id or name. The description references 'your deployments' generically and does not explain the single-deployment filter or what happens when it is omitted (all deployments, presumably), so it adds no meaning beyond the schema. 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 resource and scope: health of deployments that send witnessed data, explicitly enumerating the ingestion paths (Ingest API, SDK, OpenTelemetry, own agent platform account). An agent can tell it is a health/monitoring read on ingest pipelines. It does not, however, distinguish itself from adjacent siblings such as get_program_status or get_agent_outcomes, so a 4 rather than a 5.

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?

Usage is implied by the scope statement — this is the tool to call when you need ingest pipeline status, late-interaction handling, or consent/reconciliation state for deployments sending witnessed data. There is no explicit when-to-use versus alternatives, and no named sibling to route to for broader program or outcome questions; prerequisites are limited to the auth note.

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