Skip to main content
Glama

List or describe data products

springroll.connect.data_products
Read-onlyIdempotent

Without dataProduct, lists the governed data products this organization publishes: what each one holds, who owns it, and how sensitive it is.

With dataProduct, returns that product's schema: its datasets, the available fields with their types and sensitivity, the business glossary its owner wrote, and what the underlying source can compute. Read this before requesting access, so you request the fields the application actually needs.

Either way you learn the kind of system behind a product (so you know, for example, which query capabilities a source supports) but never a host, a credential, a table name, or a connection string. Request access with springroll.connect.request_access; a data owner must approve it.

Input Schema

NameRequiredDescriptionDefault
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
dataProductNoData product slug. Omit to list every product this organization publishes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive context beyond them: exactly what is never exposed (host, credential, table name, connection string), what kind-of-system metadata is exposed instead, and that a data owner must approve any subsequent access request.

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?

Front-loaded conditional structure ('Without X… With X… Either way…') that an agent can parse at a glance, with no filler sentences. Each paragraph carries a distinct piece of information: list mode, detail mode, disclosure boundary, and the follow-up call.

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?

There is no output schema, and the description compensates by enumerating what comes back in each mode (ownership, sensitivity, datasets, fields with types, business glossary, source compute capabilities). Combined with the privacy boundary and the next-step routing, nothing needed to call it correctly is missing.

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%, so the schema already documents both `context` and `dataProduct`, including that omitting `dataProduct` lists everything. The description's per-mode explanation largely restates that contract, so it does not add much parameter-level meaning beyond the schema baseline.

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 gives a specific verb and resource and then splits the two modes cleanly: without `dataProduct` it lists governed products; with `dataProduct` it returns that product's schema. An agent can distinguish it from siblings like `springroll.connect.access_status` and `springroll.connect.request_access` without opening any 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 sequences this call before `springroll.connect.request_access` and states the rationale ('so you request the fields the application actually needs'), and names the sibling to use for the access request. It does not state any when-not-to-use condition, so it falls short of the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources