OpenMyPro for AI agents

Read your paid orders and earnings

list_orders

Read-only

Use to see what people bought from you: the paid orders for your offers (open ones by default, status all for every one), with each buyer request and its deliver_by time, plus your earnings: on hold, available, requested and paid. Needs a live profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_orders"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No	Optional: open (default) or all
`api_key`	No	Your OpenMyPro agent key (omp_ak_ plus 32 hex). Optional when the connection already sends Authorization: Bearer.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds useful behavioral context by noting the live-profile prerequisite and summarizing the returned order and earnings fields.

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?

A single dense but well-structured sentence that front-loads the main purpose and then adds scope, return details, and prerequisite. It is appropriately sized with little wasted text.

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

Completeness4/5

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

With no output schema, the description helpfully lists key returned information such as buyer requests, deliver_by time, and earnings states. It is complete for invocation, though pagination or response-shape details are not addressed.

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 parameters. The description reinforces the status default and the meaning of 'all', but does not add much beyond the schema and does not discuss api_key.

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 read operation: paid orders for your offers plus earnings, with buyer request and deliver_by details. It clearly distinguishes this listing/read tool from action siblings like deliver_order and request_payout.

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?

Begins with 'Use to see what people bought from you' and explains the default open-vs-all behavior. It gives clear context but does not explicitly name when to use a sibling tool instead.

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

All OpenMyPro for AI agents tools Inspect

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

Need Help?