Quiet Failures

Get one base rate in full

get_base_rate

Read-only

Full detail for one Quiet Failures base rate segment: the figure with confidence interval, how it is measured, why it matters, the limits of the measurement, the recent time series, and the canonical source URL to cite. Segment defaults to "global"; country slugs (gb, fr, us…) and company cuts (gb-companies, gb-small…) are also published.

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": {
      "metric": "<metric>"
    },
    "name": "get_base_rate"
  }
}

Input Schema

Name	Required	Description	Default
`metric`	Yes	Metric id, e.g. "dmarc-policy" (see list_base_rates)
`segment`	No	Segment slug, default "global"	global

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes beyond the readOnlyHint annotation by disclosing exactly what the output includes (measurement, importance, limits, time series, canonical source URL) and clarifying default segment behavior. This provides rich behavioral context without contradicting the read-only nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loads the core purpose, and packs useful detail without fluff. Every phrase adds value, from the list of output components to the segment type examples.

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?

Given the read-only nature, no output schema, and two simple parameters, the description provides a complete picture: what is returned, what parameters do, and possible segment values. It is sufficient for an agent to invoke correctly.

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?

The schema already describes both parameters with examples (metric id, segment slug). The description adds further meaning by explaining segment defaults and naming country/company cut examples, enriching the understanding beyond the schema.

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?

The description clearly states the tool returns 'full detail for one Quiet Failures base rate segment', listing specific content like the figure, confidence interval, measurement approach, and source URL. It specifies the metric and segment parameters, and the scope ('one segment') distinguishes it from list_base_rates while the detail level separates it from find_base_rate.

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?

The description implies usage for retrieving comprehensive details on a single segment, noting the default segment and available cut types. It does not explicitly name alternative tools or exclusion criteria, but the context is clear enough for an agent to know when to invoke this tool.

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

All Quiet Failures tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?