Skip to main content
Glama

VisibilityOS Study Reader

Read an engine view

read_engine_view
Read-onlyIdempotent

Return the published comparison count, brand-presence change count and rate for one exact engine view. Engine-specific official-link counts are unavailable in the public dataset.

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": {
      "engine_view": "<engine_view>"
    },
    "name": "read_engine_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
engine_viewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by naming the returned metrics and warning that engine-specific official-link counts are unavailable in the public dataset.

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 definition is two sentences, front-loads the returned metrics, and follows with an important data-availability caveat. There is no redundant wording or unnecessary preamble.

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?

For a one-parameter read-only tool with strong annotations but no output schema, the description adequately explains what is returned and notes a key limitation. It stops short of describing output shape or interpretation details, but the essential information needed to invoke the tool is present.

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 0%, so the description must carry the explanatory burden. It clarifies that the parameter identifies one exact engine view and adds a dataset limitation, but it does not explain case sensitivity, permitted values, or other semantics beyond what the enum already provides.

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 states a specific verb ("Return") and a precise resource: counts and a rate for one exact engine view. It distinguishes its single-view scope from a comparison-oriented sibling by emphasizing "one exact engine view," though it does not explicitly name alternatives.

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 "for one exact engine view," which suggests when this tool is appropriate. However, the description does not explicitly say when to use it instead of compare_engine_views or read_study_summary, nor does it provide 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.