Skip to main content
Glama
Sign In

Replo

by io.github.replohq
OverviewDiscussionsAdmin

Find technologies

sightglass_find_technologies
Read-onlyIdempotent

The technology directory: the apps and vendors detected on tracked brands' sites (Shopify, Klaviyo, Recharge…), ranked by how many brands use each and how those brands are doing. Pass slug for one technology's adopter stats and its category peers. To list the brands or ads behind a technology, pass its name as technologies to sightglass_find_ads or sightglass_find_site_pages. Returns data only: nothing is shown to the user yet. Once you know the answer, call sightglass_show once with this call's resultId to show it as cards; the show call does not search again. Works without a Replo account: call it before asking the user to sign in.

Input Schema

NameRequiredDescriptionDefault
slugNoOne technology's slug from an earlier result: returns its adopter stats and peers instead of the directory.
sortNo
limitNo
searchNo
categoryNoApp category as the fingerprinter labels it, e.g. email-sms
projectIdNoReplo project id, from list_projects: where the charge or the asset lands. Its workspace's plan applies.
workspaceIdNoReplo workspace id, from list_workspaces. Sets which workspace's plan applies; required when the user has more than one workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / search / maxLength
      Previous value: -200New value: +1000
  2. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / projectId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / workspaceId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint/idempotentHint already covering the safety profile, the description still adds high-value operational context: results are data-only and invisible to the user until sightglass_show is called once with the resultId, and that the show call does not re-search. It does not cover result-set paging or how ranking is computed beyond the one-line summary.

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?

Front-loaded with what the directory is, then alternatives, then the data/display workflow, then the auth note. No sentence is redundant and each carries a distinct decision the 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 7-parameter, zero-required read tool with no output schema, it covers the surprising parts well: the mandatory sightglass_show follow-up with resultId, the no-login behavior, and the slug dual mode. The main gap is that sort options and limit bounds are unexplained.

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 57%, and the description meaningfully clarifies `slug` (returns adopter stats and peers instead of the directory). However, `sort`, `limit`, and `search` are undocumented in both the description and the schema, leaving the enum values and the 40 cap unexplained at the description level.

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 first sentence names a specific resource (technology directory of apps/vendors detected on tracked brands' sites), gives concrete examples (Shopify, Klaviyo, Recharge), and states the ranking basis. It is immediately distinguishable from sightglass_find_ads and sightglass_find_site_pages, which it explicitly routes to.

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

Usage Guidelines5/5

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

It states the two operating modes precisely: no slug returns the ranked directory, `slug` returns one technology's adopter stats and category peers. It also names the sibling tools to use when the user actually wants brands or ads behind a technology, and mentions the account prerequisite is waived.

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

All Replo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources