Skip to main content
Glama
Sign In

Enrichment Crawlers MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Enrichment Data Query

query_data
Read-only

Execute Company Enrichment queries (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx'] - Get detailed body structure (replace xxxxxx with actions from available_actions)

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Common actions:

  • discovery-crawler: Find company from email domain

  • profile-crawler: Get company profile details

  • metrics-crawler: Get company metrics

  • funding-crawler: Get funding data

  • tech-stack-crawler: Detect tech stack

  • leadership-crawler: Get leadership info

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, and the description adds important behavioral context: workspace_id and available_actions must be fetched first, then action details, before constructing the body. It also lists common crawler actions, though it does not discuss rate limits or output behavior.

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 workflow step and prerequisites, then uses a compact bullet list for common actions. Minor redundancy appears in 'Follow the schema exactly' given the minimal schema, but overall the description is appropriately sized.

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?

Given a nested body object, open-world behavior, and an output schema, the description supplies the critical workflow prerequisites and common action names. Completeness is limited only by delegating the exact body shape to query_contexts, which appears intentional.

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?

The single body parameter has 0% schema description coverage, so the description must compensate. It does so partially by requiring query_contexts calls to discover workspace_id and detailed body structure, and by listing common action names, but it never defines the actual body fields itself.

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?

States a specific action—executing Company Enrichment queries—and identifies it as the final workflow step. It does not explicitly distinguish the tool from the sibling execute_action, so it is clear but not fully differentiated.

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?

Specifies REQUIRED prerequisite calls to query_contexts with request='accounts' and request='actions_details', including the exact sequence. It gives clear procedural context but does not explicitly state when not to use this tool or how it differs from execute_action.

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

All Enrichment Crawlers MCP by InsightfulPipe 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