Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

b2b_company_techstack_contacts_enricher

B2B Domain Tech Stack, Contacts, DNS & SSL Enricher: Real-time structured data extraction feed for B2B Domain Tech Stack, Contacts, DNS & SSL Enricher.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, and it delivers almost nothing: 'real-time structured data extraction' is the only behavioral hint. It never explains how the target domain is supplied, whether lookups are rate-limited or billable, what happens on an unresolvable domain, or what the returned records look like.

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

Conciseness2/5

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

It is short, but the second clause is a verbatim rephrasing of the first with no new information — pure padding rather than front-loaded substance. Every word after the colon could be deleted without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an enrichment tool with no annotations and no output schema, the description should at minimum explain what input identifies the target company/domain and what categories of data come back. Since the only parameter is maxResults, the critical question of how a domain is specified is entirely unaddressed.

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?

There is a single parameter (maxResults) with 100% schema description coverage, so the schema already documents its meaning and default. The description adds no further semantics, but the baseline of 3 is appropriate when schema coverage is this high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a near-tautology: 'B2B Domain Tech Stack, Contacts, DNS & SSL Enricher: Real-time structured data extraction feed for B2B Domain Tech Stack, Contacts, DNS & SSL Enricher.' It restates the tool name twice without a distinct verb+resource statement or any differentiation from the many other enrichment/scanner siblings (e.g. the DMARC/SPF auditor or corporate knowledge graph enricher).

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

Usage Guidelines1/5

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

No when-to-use guidance, no prerequisites, no named alternatives, and no indication of when this tool should be preferred over the dozens of sibling enrichment tools. The agent is left to infer everything from the name alone.

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

All GMPSignal Real-Time Intelligence MCP 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