Skip to main content
Glama

Analook — Competitor Intelligence

by io.github.Gingiris

browse_public_reports

Browse Analook's public competitor-intelligence report gallery.

Returns recently published public reports (product name, domain, category,
and a link). No authentication or credits required — a fast way to discover
existing analyses before spending a credit on a fresh one.

Args:
    category: Optional filter, e.g. 'AI / Agents', 'Dev Tools',
              'Crypto / Web3', 'Marketing / SEO', 'SaaS / Other'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
categoryNo
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that no auth/credits are needed and lists return fields, but does not mention pagination, result limits, sorting, or any potential rate constraints. It adds some useful context but lacks depth for a complete safety/behavior profile.

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 compact and front-loaded: first sentence states purpose, second describes output and access, third gives usage rationale, and the Args section provides a helpful parameter example. Every sentence earns its place with no fluff or redundancy.

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 simple browse tool, the description covers the main function, return fields, auth/credit requirements, and a category filter example. It lacks details on result limits, pagination, or how the link is presented, but these are minor gaps given the tool's simplicity. No output schema exists, so some return detail in the description is valued.

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 67%, and the tool description adds value primarily for the 'category' parameter with examples ('AI / Agents', 'Dev Tools', etc.). The 'context' and 'conversation_id' parameters are already well-described in the schema, so the description does not need to compensate heavily. Overall, adequate but not exceptional.

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's function: 'Browse Analook's public competitor-intelligence report gallery' and specifies what it returns ('recently published public reports (product name, domain, category, and a link)'). This distinguishes it from siblings like get_report (single report retrieval) and analyze_competitor (creating new analyses), using a specific verb and resource.

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 provides clear usage context: 'a fast way to discover existing analyses before spending a credit on a fresh one' and notes 'No authentication or credits required.' This implies when to use it (before generating new analyses), though it does not explicitly name alternatives or state when not to use it. Thus slightly short of a 5.

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

All Analook — Competitor Intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clear distinct purposes: job submission, status polling, report retrieval, and listing are separated. Some potential confusion exists between get_report/get_report_markdown (same content, different format) and get_report_status/get_growth_audit (both return status for different job types), but descriptions clarify these boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: analyze_competitor, browse_public_reports, get_growth_audit, get_report, get_report_markdown, get_report_status, list_my_reports, run_growth_audit. No mixed conventions or camelCase.

Tool Count5/5

8 tools is well-scoped for a competitor intelligence server, covering two distinct workflows (competitor analysis and growth audit) plus report browsing and retrieval. Each tool serves a clear purpose without feeling bloated or skeletal.

Completeness4/5

The core lifecycle is covered: submit analysis, poll status, fetch report in JSON/Markdown, list personal reports, and browse public reports. Minor gaps remain, such as no way to list past growth audits or cancel/delete jobs, but these are not critical for the primary use case.

Resources