Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_domain_trust_composite

Evaluate domain trust for compliance checks using SPF/DMARC grades, security headers, certificate history, and an overall trust score.

Instructions

[Compliance & Trust] Domain trust report: SPF/DMARC grade + security headers + certificate history + overall trust score Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.com.

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": {
      "domain": "<domain>"
    },
    "name": "caelara_compliance_domain_trust_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add useful behavioral context: measured p50/p95 latency, a dated benchmark source, and the upstream endpoint being called. It says nothing about authentication needs, rate limits, quotas, or whether results are cached or live.

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?

Very short and front-loaded, with the resource named first and performance data last. Formatting is slightly cramped (component list, benchmark, and endpoint run together without separators), but nothing is wasted.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should explain what the report returns — the scale or range of the trust score, the structure of the grade and certificate-history sections. It lists the section names but not their shape or interpretation, leaving a real gap for a composite tool.

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 the single required `domain` param documented as "Domain name, e.g. example.com". The description adds no further meaning on accepted formats, IDN/port handling, or normalization, so the schema does the work and 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?

The description names a specific resource and the exact components it aggregates: SPF/DMARC grade, security headers, certificate history and an overall trust score. That clearly marks it as a composite roll-up. It does not explicitly distinguish itself from the sibling single-purpose tools (spf_dmarc_grader, security_headers_audit, ssl_cert_inspector), whose subject matter it overlaps.

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?

There is no when-to-use or when-not-to-use guidance and no reference to the individual checks this report bundles. An agent must infer from the component list that this is the one-shot aggregate rather than a targeted single-check call.

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

Deploy Server

Other Tools