Skip to main content
Glama
Sign In

Hyreflow

by ai.hyreflow
OverviewDiscussionsAdmin

hyreflow_dataset_read

Read-only

Read a page of rows from a stored dataset (ds_…): at most 100 rows per call (default 25), paged with offset. The reply carries has_more and next_offset. format is json (default, row objects) or csv (the same rows as one CSV string, identical cells to the exported file and far fewer tokens). columns returns only those fields, named by key or dotted path into nested rows (e.g. ["attributes.title","attributes.first_seen_at"]), and raises the page cap to 500 rows; a path a row lacks reads as null. Any page stops early at about 60,000 characters (then limit is the rows served and next_offset resumes the read). A dataset another workspace owns reads as 'dataset not found'. Free.

Input Schema

NameRequiredDescriptionDefault
limitNo
formatNo
offsetNo
columnsNo
dataset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / columns
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: discloses the default and hard page caps, the 500-row raise via columns, the ~60,000-character truncation with has_more/next_offset resume semantics, missing-path-as-null behavior, and cross-workspace 'dataset not found'. These are the operational traits an agent needs.

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?

Dense but front-loaded: capability, caps, paging, format, columns, truncation, and auth scoping each appear in a purposeful sentence. No filler despite length.

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

Completeness5/5

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

With no output schema and no schema descriptions, the description fully covers return shape (row objects, CSV string, has_more/next_offset), multi-workspace behavior, and caps. An agent can call it correctly without other sources.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does: limit (default 25, cap 100, raised to 500 with columns), offset paging, format enum with default and token implications, columns accepting keys/dotted paths with null fallback. Every parameter gains meaning beyond the bare schema.

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 and resource ('Read a page of rows from a stored dataset') and pins down the dataset id prefix (ds_…). Clearly distinguishable from siblings like hyreflow_dataset_export and hyreflow_datasets_list.

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?

Explains when to prefer csv (far fewer tokens) and that it's free, and clarifies paging via offset. However it doesn't explicitly contrast with a sibling such as hyreflow_dataset_export (e.g., use export for whole dataset, read for paging), so routing guidance is somewhat implicit.

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

All Hyreflow 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