Skip to main content
Glama

shiply

by now.shiply
OverviewDiscussionsAdmin

Query records from a collection

data_query
Read-only

Page records from an owned site's collection, newest-first. limit ≤ 200 (default 50). cursor from a previous response's nextCursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesowned site slug
limitNomax records to return, ≤200 (default 50)
cursorNonextCursor from a previous response's page
collectionYescollection name from data_list_collections

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / collection / description
      Added value: +"collection name from data_list_collections"
    • addedInput schema / properties / cursor / description
      Added value: +"nextCursor from a previous response's page"
    • addedInput schema / properties / limit / description
      Added value: +"max records to return, ≤200 (default 50)"
    • addedInput schema / properties / slug / description
      Added value: +"owned site slug"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds behavioral context: returns records newest-first and paginated. Could disclose rate limits or auth needs, but ordering and pagination are valuable additions.

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?

Two sentences, no extraneous words. Every sentence provides essential information about pagination, ordering, and constraints. Highly efficient.

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?

Given 4 parameters, annotations, and output schema existence, the description covers pagination mechanism, parameter constraints, and ordering. No major gaps for a paginated read tool.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds defaults for limit (50) and source for cursor (previous nextCursor), plus clarifies slug and collection context beyond schema descriptions.

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?

Description clearly states the verb 'page records', the resource 'owned site's collection', and ordering 'newest-first'. It distinguishes from sibling tools like data_insert and data_list_collections by specifying pagination and ordering.

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?

Provides concrete usage constraints: limit ≤200 (default 50), cursor from previous nextCursor. However, it does not explicitly compare to alternatives like data_export_collection for full exports.

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

All shiply toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources