Skip to main content
Glama

Attify

Explain a check

explain_check
Read-onlyIdempotent

What one check of a job type's standard asks, which question it answers (did it happen, did it stick, did a human have to redo it) and which evidence tier decides it. Checks by job type: support-resolution: "repeat_contact", "handoff", "judge_unresolved"; sales-meetings: "not_ai", "not_new", "stepped_in", "cancelled", "no_show", "not_sales"; bookings: "not_ai", "not_new", "staff_fixed", "cancelled", "no_show", "wrong_booking".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "check": "<check>"
    },
    "name": "explain_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkYesThe check key, e.g. "repeat_contact" or "no_show".
job_typeNoOne of "support-resolution" (the default), "sales-meetings", "bookings".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds that the answer includes what the check asks and which evidence tier decides it, giving a useful handle on the shape of the response even without an 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?

The core statement is front-loaded and the per-job-type lists are dense but earn their space because the schema has no enums for check keys. The single long paragraph is a bit unwieldy but not padded.

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?

For a two-parameter read tool with no output schema, the description supplies the full valid check-key domain and a summary of the answer's contents. Only the behavior for unknown keys or missing job_type is left unstated, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by enumerating the concrete check keys available for each of the three job types, information the schema does not carry (it only shows two examples and no enums). It also reinforces the default job_type indirectly through the grouping.

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 states a specific resource ('one check of a job type's standard') and what the answer covers: the question it asks and the evidence tier that decides it. It is clearly narrower than get_standard or explain_provenance, though it never names a sibling to sharpen the distinction.

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 enumerating the valid check keys per job type, which tells an agent when this tool applies. There is no explicit when-to-use vs. get_standard/explain_provenance guidance or any exclusion, so it stops short of full routing.

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