Skip to main content
Glama
SignalGrid B2B Intelligence MCP

SignalGrid B2B Intelligence MCP

preview_sample_b2b_dataset

Read-onlyIdempotent

Preview up to 50 verified offline sample rows from bundled Xero, QuickBooks, or FDA datasets to evaluate B2B data without an API key.

Instructions

Read verified offline sample rows (up to 50 records) from the bundled Xero App Store, QuickBooks App Store, or US FDA Import Refusal datasets with zero API key required.

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": {
      "dataset": "<dataset>"
    },
    "name": "preview_sample_b2b_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of sample records to return (1-50).
datasetYesWhich bundled B2B dataset to preview: 'xero', 'quickbooks', or 'fda'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. Beyond that, the description adds genuinely useful facts: the data is bundled offline, the result is capped at 50 rows, and no API key or auth is needed. It simply omits return shape and whether rows are stable across calls.

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

Conciseness5/5

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

One front-loaded sentence carries the action, the resource, the size cap, the dataset choice, and the auth fact with zero filler. Nothing could be cut without losing signal.

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 sampler with no output schema, the description covers what is needed to call it correctly: which datasets, how many rows, and that no credentials are required. Only the shape of the returned sample rows is left unstated, which is a minor gap for a preview tool.

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 description coverage is 100%, with the enum values and the 1-50 limit range already documented in the schema. The description's 'up to 50 records' restates the schema maximum rather than adding new meaning, so the baseline of 3 applies.

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?

The description gives a specific verb (read) and resource (verified offline sample rows) drawn from three named datasets, and the word 'sample' plus the 50-record cap distinguishes it in spirit from the sibling extract_* tools that pull full lead sets. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiated.

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?

The phrase 'zero API key required' and 'sample rows' implies a low-commitment trial call, and the enum of three datasets is spelled out. However, there is no explicit when-to-use or when-not guidance, and nothing tells the agent to prefer this over the extraction siblings for full data pulls.

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