Skip to main content
Glama

VisibilityOS Study Reader

Read the VisibilityOS study

read_study_summary
Read-onlyIdempotent

Return the study's published totals, presence gains and losses, official-link changes, and per-view counts. Use for aggregate questions about this specific study and its methodology.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_study_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. With no output schema, the description earns credit for disclosing the return contents (totals, gains/losses, link changes, per-view counts), though it says nothing about freshness, weighting, or whether counts are truncated.

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 sentences, no filler: the payload is front-loaded and the usage cue follows. Every clause maps to something an agent needs.

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 zero-parameter read tool with no output schema, the description adequately covers what is returned and when to call it. Minor gaps remain around data currency and whether the figures are normalized or raw, which matter for interpreting methodology-adjacent questions.

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 tool takes zero parameters, so the schema imposes no undocumented surface and the baseline applies. The description correctly doesn't invent parameters and instead spends its words on scope and return contents.

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?

"Return the study's published totals, presence gains and losses, official-link changes, and per-view counts" names a concrete verb and enumerates exactly what comes back, so the agent knows the payload shape without opening anything. The second sentence scopes it to aggregate questions about this one study, which implicitly separates it from the per-engine siblings read_engine_view and compare_engine_views.

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?

"Use for aggregate questions about this specific study and its methodology" gives a clear triggering context and limits the scope to one study's aggregates. It stops short of naming when not to use it (e.g., per-engine breakdowns or cross-study comparison), so the routing is inferable rather than explicit.

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.