Skip to main content
Glama
Sign In

ShootProof MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List orders in ShootProof

shootproof_list_orders
Read-onlyIdempotent

List orders in the user's own ShootProof account from ChatGPT, Claude or any AI agent. Returns how to do it in ShootProof step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ShootProof Cloud Browser. ShootProof's official API: ShootProof has a documented OAuth API that is free with an account, but you get a client ID only by emailing ShootProof support with your app details (checked 8 Nov 2026).

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": "shootproof_list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral detail beyond that: it 'opens nothing by itself' and returns screens, buttons, and fields rather than performing the action. The OAuth API note also explains why browser automation is needed, without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and useful, but the description then includes a long API/OAuth aside and the 'ChatGPT, Claude or any AI agent' phrasing, which are not essential for invoking this 0-param tool. The structure is readable but not as tight as it could be.

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?

Given the low complexity, no parameters, and no output schema, the description covers the practical return behavior: step-by-step screens, buttons, and fields, followed by browser tools. It does not specify the exact output format, but it provides enough context for an agent to call and use the tool correctly.

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?

This tool has zero parameters, so there are no parameter semantics to explain; the baseline for a 0-param tool is 4. The description appropriately does not invent parameters or imply hidden inputs.

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: 'List orders in the user's own ShootProof account.' It then clarifies that it returns step-by-step instructions rather than opening anything, which is important context, though the opening still slightly implies direct listing. It is clear enough to select, but not as sharply differentiated from sibling guide tools as it could be.

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?

Explicitly tells the agent how to proceed: after this tool, 'do it with the cotlet_browser_* tools in the user's ShootProof Cloud Browser.' That gives a concrete workflow and context. It does not name when-not to use it or compare directly with cotlet_app_guide, but the intended usage path is clear.

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

All ShootProof MCP Server and API by Cotlet 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