Skip to main content
Glama
Sign In

AI Web Research & Research Brief Agent

by io.github.industrial-platform-ai
OverviewDiscussionsAdmin

Server Details

x402 cited web research and synthesis for agents. $1.99 per completed brief.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
industrial-platform-ai/industrial-platform-agent-tools
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 5 tools

Disambiguation4/5

The four Apify infrastructure tools target clearly different resources: run control, run status, dataset rows, and key-value records. The research-brief-agent tool is domain-specific, though it partially overlaps conceptually with get-actor-run/get-dataset-items because it also runs an Actor and retrieves output.

Naming Consistency3/5

Most tools follow a readable kebab-case verb-resource pattern such as abort-actor-run, get-actor-run, get-dataset-items, and get-key-value-store-record. However, industrial_platform--research-brief-agent uses snake_case with a double hyphen and is named after an external Actor rather than following the verb_noun convention.

Tool Count5/5

Five tools is a well-scoped size for this server: one primary research-brief operation plus four supporting Actor-run and output-retrieval tools. There is no obvious bloat or excessive tool count.

Completeness3/5

The core research flow is covered: start/retrieve a brief, check run status, abort a run, and read dataset or key-value outputs. But the surface lacks important companion operations such as listing datasets, listing keys in a key-value store, or generic Actor run creation, which can create dead ends when identifiers are unknown.

Available Tools

5 tools
abort-actor-runAbort Actor runA
DestructiveIdempotent
Inspect

Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.

USAGE:

  • Use when you need to stop a run that is taking too long or misconfigured.

USAGE EXAMPLES:

  • user_input: Abort run y2h7sK3Wc

  • user_input: Gracefully abort run y2h7sK3Wc

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Inputs: runId (required), gracefully. Returns: object

get-actor-runGet Actor runA
Read-onlyIdempotent
Inspect

Get detailed information about a specific Actor run.

Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.

  • summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").

  • nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").

  • waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.

USAGE:

  • Use to check the status of a run started by any Actor-running tool.

  • Pass waitSecs > 0 to block until terminal (or until the cap elapses).

USAGE EXAMPLES:

  • user_input: Show details of run y2h7sK3Wc

  • user_input: Wait for run y2h7sK3Wc to finish

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Inputs: runId (required), waitSecs. Returns: object

get-dataset-itemsGet dataset itemsA
Read-onlyIdempotent
Inspect

Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.

USAGE:

  • Use when you need to read data from a dataset (all items or only selected fields).

USAGE EXAMPLES:

  • user_input: Retrieve results from dataset abc123

  • user_input: Get only metadata.url and title from dataset username~my-dataset

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Inputs: datasetId (required), desc, omit, clean, +4 more. Returns: object

get-key-value-store-recordGet key-value store recordA
Read-onlyIdempotent
Inspect

Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically.

USAGE:

  • Use when you need to retrieve a specific record (JSON, text, or binary) from a store.

USAGE EXAMPLES:

  • user_input: Get record INPUT from store abc123

  • user_input: Get record data.json from store username~my-store

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Inputs: recordKey (required), keyValueStoreId (required). Returns: object

industrial_platform--research-brief-agentindustrial_platform/research-brief-agentA
Destructive
Inspect

This tool calls the Actor "industrial_platform/research-brief-agent" and retrieves its output results. Actor description: Use for current cited multi-source research, comparisons, and fact verification. Returns a synthesized brief with citations. $1.99 per completed brief; failed runs are not billed.

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Inputs: research_question (required), context, waitSecs, requirements. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    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