Skip to main content
Glama
Sign In

Andru

by io.github.geter-andru
OverviewDiscussionsAdmin

Preview a company

preview_company
Read-only

Before any outreach: use this when the person wants to see how a company's website reads to the buyers it wants, before they have an Andru account. Returns who the company sells to, the buyers who decide, and what the site says versus what those buyers need to hear. Send the website. No account needed. Takes about a minute: you get a preview_id; call again with it to collect the read. If the person signs up with signup_start and this preview_id, the read becomes their first ICP.

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

Input Schema

NameRequiredDescriptionDefault
websiteNoThe company's website, e.g. acme.com.
previewIdNoFrom an earlier call, to collect the read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the genuinely missing behavior — the call is asynchronous and two-phase (first call yields a preview_id, second call collects the read), takes roughly a minute, and requires no authentication. It also discloses that the artifact persists into the account if signup_start uses the same preview_id, which is non-obvious state coupling.

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

Conciseness4/5

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

Front-loads the timing constraint and the no-account condition, then the return shape, then the mechanics — a sensible order for a two-step tool. The staccato fragments ("Send the website. No account needed.") are efficient but slightly clipped, and the signup_start note could be tighter.

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 two-parameter, no-output-schema tool it covers purpose, return content, latency, the polling pattern, and cross-tool state. The remaining gap is operational edge cases — preview_id expiry, re-use, or failure after the second call — which an agent would have to discover by trial.

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?

With 100% schema coverage the baseline is 3, but the description earns a bump by explaining the round-trip relationship between the two fields rather than treating them as independent inputs. It does not clarify that both are technically optional or what happens if neither is supplied.

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?

States a concrete verb+resource (preview a company's website as buyers read it) and enumerates what comes back: who the company sells to, the deciding buyers, and site-vs-need gap. It also positions itself against the account-holding path, so an agent can separate it from siblings like get_icp_profile or assess_company_readiness.

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?

"Before any outreach" plus "before they have an Andru account" gives a clear trigger condition and an implicit exclusion (account holders should use the ICP tools instead). It also names the downstream handoff to signup_start with the returned preview_id, though it never states what to do if the person already has an account or the preview stalls.

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

All Andru 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