Skip to main content
Glama
SreeTarak2

DataFlow MCP Server

by SreeTarak2

get_records_for_events

Retrieve raw event URLs and the event-structuring schema in one call, enabling a chatbot to extract and organize conference, workshop, meetup, and webinar details into structured documents.

Instructions

Fetch raw records + the Events prompt (event-structuring-v1.1.txt, events-v1.1 schema) so a chatbot can structure participatory events (conferences, workshops, meetups, webinars, summits, trainings).

Use this when you want to go from raw event URLs/titles to a structured event document in one AI round-trip. The chatbot should:

  1. Read the event prompt_text (events-v1.1 schema and rules)

  2. For each record, pin the target event (name, edition, location, domain) and hunt the official site's subpages (speakers, agenda, pricing, venue)

  3. Extract fields following the events-v1.1 schema

  4. Return ONE event JSON per record via submit_structured_events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum raw records to fetch (default 10, max 25).
sourceNoFilter by scraper source field (e.g. "women_opportunities_aug_2026"). If None, all records in the collection.
collection_nameNoRaw DB collection to read from. Defaults to "raw_urls" (the collection of URLs harvested from the women-opportunities text file); pass the pipeline collection name to reuse aggregation.raw_urls

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the fetch operation and the workflow, and implies read-only behavior, but does not explicitly state side effects, rate limits, or constraints beyond what the schema covers.

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?

The description is moderately concise, with a clear first sentence and a numbered workflow. The step-by-step instructions add value but could be tightened.

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 the output schema exists and the description provides a full workflow with the expected interaction with submit_structured_events, it is quite complete. It could mention the limit on records, but that's in the schema.

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%, so the schema already documents all three parameters with descriptions. The tool description does not add any parameter-specific meaning, but it does not need to.

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?

The description clearly states the tool fetches raw records plus an events structuring prompt, using specific verbs and resources. It distinguishes itself from siblings by focusing on participatory events and the events-v1.1 schema.

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?

It explicitly states 'Use this when you want to go from raw event URLs/titles to a structured event document in one AI round-trip' and provides a step-by-step workflow. It does not explicitly name alternative tools or when not to use it, but the context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SreeTarak2/dataflow_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server