Skip to main content
Glama

Serpier

by com.serpier
OverviewDiscussionsAdmin

get-orders

Read-only

Get orders for the organization. Use the typed filters array: each entry needs columnId (status, createdByUserId, assignedToSalesUserId, createdAt), type, values, and operator. Multiple filters combine with AND; use 'is any of' for multiple values on one column. For createdAt date ranges use operator 'is between' with two ISO date strings (YYYY-MM-DD). If this tool returns { ok: false, error }, it failed. Explain the error to the user concisely in plain language and ask them to help resolve it (for example, select a valid project) — do not retry the same call blindly.

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
searchNo
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
filtersNoArray of filters to apply. Multiple filters are combined with AND logic. To match ANY of several values on the same column, use ONE filter with the 'is any of' operator.
orderByNo
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
organizationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/not-destructive, so the safety profile is covered. The description adds valuable behavioral context by explaining the `{ ok: false, error }` failure contract and instructing the agent not to blindly retry, which annotations don't convey.

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?

Front-loads the core action, then the filter mechanics, then error handling – a sensible order. A couple of clauses on operators are somewhat redundant with the filter sub-schema descriptions, but overall it is tight and earns its space.

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?

For an 8-parameter list tool with no output schema, the description covers filters and error handling but omits pagination (page/limit), search, orderBy, and organization scoping. These gaps leave the agent guessing on several non-trivial parameters.

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 low (38%), but the description compensates well for the most complex parameter, `filters`, detailing columnId values, type, operators, AND semantics, and ISO date format with 'is between'. It leaves page, limit, search, orderBy, and organizationId undocumented, so it isn't fully complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get orders for the organization'), making the operation clear. It doesn't differentiate from the singular 'get-order' sibling, so an agent must infer that this returns a list while the other fetches one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides detailed guidance on how to build filters (AND combination, 'is any of', date ranges), but never addresses when to choose this tool over 'get-order' or other siblings. Usage is implied rather than explicitly scoped against alternatives.

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

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