Autopo

Get decision

get_decision

Read-onlyIdempotent

One inbox card in full: the ask, the agent's case, the options, the work behind it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "decision": "<decision>"
    },
    "name": "get_decision"
  }
}

Input Schema

Name	Required	Description	Default
`decision`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026

addedInput schema / $schema

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

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

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

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds useful content about what a card contains (ask, agent's case, options, work behind it), which goes beyond the annotations, but it says nothing about not-found behavior, permissions, or how the card is addressed. An output schema exists, so the return shape itself doesn't need spelling out here.

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?

One short, front-loaded sentence with no filler. It's efficient, though the poetic framing costs some precision.

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?

With annotations handling safety and an output schema defining return shape, the remaining gap is how to identify the decision and when to reach for this versus list_decisions. The description leaves both unaddressed, which is a meaningful omission for the only required parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'decision' parameter, and the description never mentions it. It's unclear whether 'decision' is an ID, slug, or card reference, which is exactly the information the description should supply when the schema does not.

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

Purpose3/5

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

The phrase 'One inbox card in full' signals a single-item fetch, and the field list (ask, case, options, work) hints at the resource, but it never uses a concrete verb like 'retrieve' or names the resource 'decision'. It also doesn't distinguish itself from the sibling list_decisions, so the purpose is implied rather than stated.

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

Usage Guidelines2/5

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

There is no statement of when to use this instead of list_decisions, decide, or comment_on_decision. An agent must infer the use case entirely from the name and metaphor.

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?