Skip to main content
Glama

Peer study, latest

research
Read-only

The latest study of up to 8 products a step ahead of this one, each found through a lens (peers[].lens) or named by the founder (via "founder"; named lists the ones kept for every study): same_job (it does this product's job, in any form; peers[].job says whether the whole job or one piece of it, and launchedAt when it launched), same_buyers (its buyers also pay for it), same_shape (sold and installed the same way). What each shows in public today (the first screen, the way to signup, pricing, free tools, launches, listings, top X posts) and how it started (read.early: its home page in the Wayback Machine's first captures, its launches with points, its early posts), and the patterns: today (two or more do it and this site does not) or early (an early move, one product enough when it has outside proof), each with the products' pages, their own words, a first step for this product, its key and the move it becomes. For an iOS app the products are apps (peers[].app, read on the App Store; peers[].domain is the app's key, id.apps.apple.com): the apps that top the app's own App Store searches with more ratings, each with its listing (name, subtitle, price, in-app purchases, rating and ratings, screenshots, version dates) and what its reviews say about the trial, price, subscription, paywall and ads; the app's own listing is founder.app, and each pattern's move is a part of the aso routine. Patterns already done (recorded with meta.research) and products removed with research_skip are left out. Also whether one is running, when the next free one is, and the price of one now. Free.

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": "research"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already mark it read-only and non-destructive; the description adds substantive behavior: up to 8 products, exclusion of completed patterns and research_skip removals, an iOS App Store mode, and free/running status. It does not disclose auth or response-format details, but it goes well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is a dense block with nested parentheses, semicolons, and slash-delimited lists, making it hard to scan. Much detail may be useful, but it is not front-loaded or structured into digestible sections.

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?

Because there is no output schema and no parameters, the description must carry the return-value burden; it does so extensively for both web products and iOS apps, including exclusions and pricing/free-run information. It is sufficiently complete for a read-only retrieval tool, though clarity suffers.

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 there is no parameter semantics for the description to clarify. The empty schema has full coverage by definition, and the baseline of 4 applies.

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 opening clause names a specific resource and scope: 'The latest study of up to 8 products a step ahead of this one.' It then specifies peer lenses and iOS-specific behavior, and it distinguishes itself from research_skip by noting skipped products are excluded. It does not explicitly separate itself from research_run, but the purpose is still clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No sentence says when to call this tool instead of research_run or other research siblings. The reader can infer it retrieves the latest completed study, and the mention of running status and next free slot implies capacity checks, but there is no explicit when/when-not guidance.

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.

Resources