Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

list_available_intelligence_actors

Read-onlyIdempotent

Discover, search, and filter 40 GMPSignal Apify Actors by vertical, keyword, and pay-per-event pricing without using API credits.

Instructions

Discover, search, and filter all 40 GMPSignal Apify Actors by intelligence vertical (crypto, b2b, compliance, regional), keyword, and Pay-Per-Event pricing without consuming API credits.

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

Input Schema

NameRequiredDescriptionDefault
suiteNoVertical suite filter to inspect.all
keywordNoOptional keyword to filter Actor slugs or descriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower; the description still adds a genuinely useful operational fact — calls consume no API credits. It also discloses the catalog size (40 actors) and that pricing metadata is exposed. It stops short of describing result ordering or response shape, but that is a minor gap given the annotation coverage.

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?

A single front-loaded sentence that leads with the verb and resource, then enumerates filter axes, then the cost benefit. It is dense and mostly earns its words, though the pricing clause is longer than needed given there is no pricing parameter.

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 trivial two-parameter, zero-required, read-only catalog tool with no output schema, this defines scope, filter axes, and the no-credit cost model adequately. Adding a hint about what each returned entry contains, or the browse-before-invoke workflow, would make it fully complete.

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 coverage is 100% and both parameters carry descriptions with a default and enum values, so the schema does the heavy lifting. The description reinforces the vertical and keyword axes but adds no format or semantics beyond them, and it mentions filtering by Pay-Per-Event pricing even though no pricing parameter exists, which slightly misleads about what can actually be constrained.

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 specific verb set (discover, search, filter) plus the exact resource (all 40 GMPSignal Apify Actors) and the axes of filtering (vertical, keyword, pricing). This is clearly a catalog/browse tool, distinct from the sibling tools which are individual analysis and data tools.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description makes clear this is a discovery surface over the actor catalog, but it never says to call this before or instead of the specific actor tools, nor does it set exclusions. An agent can infer the browse-first role, but it is not spelled out.

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