coherence-signal

compare_brands

Compare the NES coherence signal for several brands side by side (claim, reality, divergence for each). Presents the data; it does NOT recommend one brand over another. The caller decides.

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": {
      "urls": "<urls>"
    },
    "name": "compare_brands"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes	Brand URLs or domains to compare (up to 8).

Output Schema

Name	Required	Description	Default
`brands`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 20, 2026

TDQS

A3.8/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only adds that the tool 'does not recommend', but does not disclose read-only behavior, auth needs, rate limits, or any side effects. Inadequate for a mutation-ambiguous context.

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?

Two succinct sentences with no filler. Front-loaded purpose, then key caveat. Every sentence earns its place.

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?

Given the output schema exists, description does not need to detail returns. It covers the essential purpose and limitation. Could mention prerequisites or when to use the sibling, but it's adequate for a simple tool with one parameter.

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 includes the 'up to 8' constraint. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Clearly states 'Compare the NES coherence signal for several brands side by side', which is a specific verb+resource+format. Distinct from sibling 'get_brand_coherence' which likely handles single brands.

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?

Implicitly indicates use for multi-brand comparison and clarifies it does not recommend. However, no explicit mention of when to use vs. sibling or when-not to use.

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

All coherence-signal 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?