Skip to main content
Glama

VisibilityOS Study Reader

Compare two engine views

compare_engine_views
Read-onlyIdempotent

Compare the published brand-presence change rates of two engine views in the VisibilityOS study. Return both denominators and the first rate minus the second in percentage points.

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": {
      "first_view": "<first_view>",
      "second_view": "<second_view>"
    },
    "name": "compare_engine_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
first_viewYes
second_viewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral value by disclosing the return content (both denominators plus a signed percentage-point difference), which is exactly what an agent needs to interpret a result. It stops short of describing error behavior for invalid view names.

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 short sentences, front-loaded with the purpose and followed by the return shape; nothing is redundant or 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?

With no output schema, the description correctly takes on the burden of explaining the return values, including units. The only residual gap is that 'change rate' itself is not defined beyond its brand-presence context, though that is likely shared study vocabulary.

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 0% but both parameters are closed enums with self-describing names. The description still earns credit by stating that the output is 'the first rate minus the second', which fixes the direction and sign convention of the comparison — information the schema alone does not convey.

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?

Names a specific verb ('Compare'), specific resource ('engine views'), and scopes it to 'published brand-presence change rates' in a named study, plus states what the result is. It is clearly distinguishable from a plain read of one view, which is what a sibling like read_engine_view would do.

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 the word 'Compare' and the requirement for two views, so an agent can infer this is the tool for A-vs-B questions. However, it never states when to prefer it over reading views individually or over a summary tool, and offers no exclusions or prerequisites.

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.