Skip to main content
Glama

emet_error_report

Read-onlyIdempotent

Read the operational error log and show a report the owner can send on. Owner only. Read-only: it writes nothing and sends nothing. EMET has no mail sender and opens no network connection for this tool.

Instructions

Read the operational error log and show a report the owner can send on. Owner only. Read-only: it writes nothing and sends nothing. EMET has no mail sender and opens no network connection for this tool. The result is the full report, then a mailto link, then a structured email {to, subject, body_text, short_id, version} a calling assistant can pass to its own email tool. The calling assistant may send this report only after showing the report to its user and getting their OK.

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

Input Schema

NameRequiredDescriptionDefault
codesNoOptional list of EMET codes to include.
limitNoHow many of the most recent entries to list. Default 50, maximum 200.
sinceNoISO date (YYYY-MM-DD) or UTC timestamp. Default is 7 days ago. Cannot be older than 90 days.
correlation_idNo16 hex characters from an error response. When set, since is ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotent, non-destructive, but the description adds real value beyond them: it writes nothing, sends nothing, has no mail sender, and opens no network connection. It also defines the return shape (full report, mailto link, structured email with field names) and the human-approval requirement for sending.

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-loads purpose, owner scope, and read-only safety before the return-format and approval details. It is fairly dense—the mailto/structured-email sentence packs multiple facts—but each sentence contributes actionable information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by describing the return sequence (report, mailto link, structured email {to, subject, body_text, short_id, version}). Combined with the safety and owner-only constraints, an agent has everything needed to call and handle the result correctly.

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%, with all four parameters including defaults, maximums, the 90-day limit, and the correlation_id/since override already documented. The description adds no parameter-specific syntax or examples, so the schema carries the burden and baseline 3 applies.

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

Purpose5/5

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

States a specific verb+resource: reads the operational error log and produces a report the owner can send on. It distinguishes itself from siblings (transcript, page, status, gaps) by being the error-log read path, and adds an owner-only scope. An agent can identify what this does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditions: owner only, and the calling assistant may send only after showing the report to its user and getting their OK. It implies the send-report workflow but does not explicitly name alternatives among the many emet_* siblings, so it is strong context rather than full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.