Autopo

Inbox

list_decisions

Read-onlyIdempotent

The Board inbox: cards waiting for you (status pending, default), or decided ones. Each card says what the team wants, why, the risk tier and the amount; decide with decide.

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_decisions"
  }
}

Input Schema

Name	Required	Description
`page`	No
`status`	No	pending (default), decided, or a comma list
`company`	No	the company id (list_companies); not needed when you have one company, asked for otherwise
`page_size`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 2, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / company / description

Previous value: -"the company id (list_companies); optional when you have one"New value: +"the company id (list_companies); not needed when you have one company, asked for otherwise"

addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```
removedInput schema / required
```
Removed value: -[]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely new context: what each card contains (the ask, the rationale, risk tier, amount), which helps an agent know what to expect from the payload.

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 compact sentences with zero filler; the scope/default comes first and the actionable next step (`decide`) is placed at the end where it reads as a follow-up.

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 an output schema present and strong annotations, the description needn't explain return shape, and it covers the primary filter and card contents. The remaining gap is pagination and the `company` requirement condition, which the schema only partially documents.

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?

At 50% schema coverage, the description explains `status` semantics (pending default, decided) in a way that complements the schema. It says nothing about `page`, `page_size`, or `company`, leaving pagination and the multi-company case undocumented in both places.

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?

The description identifies the resource (the Board inbox cards) and the scope filter (pending by default, or decided), which lets an agent tell it apart from `decide` and `get_decision`. The verb 'list' is only implied by 'inbox', but the intent is unambiguous in practice.

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?

It states the default status filter and points to `decide` for acting on a card, which is useful routing. However, it gives no guidance on when to use this versus `get_decision`, `app_refresh_inbox`, or `comment_on_decision`, so the sibling differentiation is partial.

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

All Autopo 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?