Skip to main content
Glama
asaje379
by asaje379

query-objects

Fetch Parse objects from a class using MongoDB-style filters, with sorting, pagination, field selection, and pointer inclusion.

Instructions

Query objects from a Parse class with filters, sorting, and pagination. Supports MongoDB-style query operators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination
countNoInclude total count of matching objects
limitNoMaximum number of results to return (default: 100)
orderNoField to sort by. Prefix with '-' for descending order (e.g., '-createdAt')
whereNoQuery filters using MongoDB-style operators ($eq, $ne, $lt, $lte, $gt, $gte, $in, $nin, $exists, $regex, $contains, $startsWith, $endsWith)
selectNoArray of fields to return (projection)
includeNoArray of pointer fields to include (populate)
classNameYesThe name of the Parse class to query
Behavior4/5

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

With no annotations, the description carries the burden of indicating safety. The verb 'Query' clearly implies a read-only operation, and mentioning 'MongoDB-style query operators' adds behavioral context. It does not explicitly state there are no side effects, but the read-only nature is strongly inferred.

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?

The description is one concise sentence that is front-loaded with the core purpose and includes high-level capabilities. There is no wasted wording or redundant information.

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

Completeness3/5

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

The tool has 8 parameters and no output schema or annotations. The description provides a high-level overview but lacks explicit usage guidelines (e.g., when to choose this over sibling query tools) and does not describe return values. The rich schema compensates partially, but the description alone is not fully complete for a complex query 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%, so each parameter is already documented. The description adds minimal extra value beyond the schema, only referencing 'MongoDB-style query operators' which relates to the 'where' parameter. This is a slight bonus, but not a significant departure from the 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 states a clear verb ('Query'), a specific resource ('objects from a Parse class'), and key capabilities (filters, sorting, pagination). The name 'query-objects' distinguishes it from sibling tools like 'query-users' and 'query-roles', which target specific classes.

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?

The description clearly indicates this tool is for querying any Parse class, which provides context for use. However, it does not explicitly mention alternatives or when not to use it compared to similar sibling tools like 'query-users' or 'aggregate'.

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/asaje379/parse-mcp-server'

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