Skip to main content
Glama

Analook — Competitor Intelligence

by io.github.Gingiris-1031

get_report_status

Poll an analysis job's status.

Args:
    job_id: ID returned from analyze_competitor()

Returns:
    {status: 'running'|'completed'|'failed', progress?: str, report_url?: str}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
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."
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.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It provides the return format (status, progress, report_url) but doesn't mention error behavior or whether polling is idempotent. This is adequate but not comprehensive.

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 well-structured, with a purpose statement, an args section, and a return format. Every sentence adds value with no filler.

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 status polling tool, the description provides the return schema and job origin. It doesn't cover error handling or conversation_id, but those are partially handled by the schema, making it sufficient overall.

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 schema lacks description for job_id, and the description fills that gap by defining it as 'ID returned from analyze_competitor()'. The other parameters (context, conversation_id) already have schema descriptions, so the description doesn't need to repeat them.

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 'Poll an analysis job's status' with a specific verb and resource. It also identifies the source of the job_id as analyze_competitor(), which distinguishes it from sibling report retrieval tools.

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 indicates job_id comes from analyze_competitor(), giving clear context for when to call. It doesn't explicitly mention alternatives like get_report, but the status return shape makes the intended use obvious.

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.4/5.0
Disambiguation5/5

Each tool targets a distinct resource+action: analyze/run create jobs, get_report/get_report_markdown/get_growth_audit retrieve different output formats, status polling is separate, and the two listing tools (public vs personal) are clearly differentiated by name and description.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (analyze_competitor, browse_public_reports, get_report, run_growth_audit). The get_* verbs are consistently used for retrieval, and list_* for list operations.

Tool Count5/5

8 tools is well-scoped for a competitor intelligence API: two job submission types (competitor analysis, growth audit), retrieval in both JSON and Markdown, status polling, and listing/browsing. Each tool serves a distinct purpose with no redundancy.

Completeness4/5

The core lifecycle (submit → poll → fetch) is fully covered for both analysis types, with additional reporting and discovery features. Minor gaps exist (e.g., no cancel operation, no direct full-text retrieval of public reports), but they don't block primary workflows.

Resources