Skip to main content
Glama

outmano_list_action_plans

Read-onlyIdempotent

List your weekly AI action plans — suggested action items generated from your competitors' latest moves, each with angle, urgency, confidence, the evidence behind it, and a ~30-minute first step. Each item carries status (active/completed); items you ignored are omitted. Newest first, paginated; use limit 1 for just the current plan.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results per page (default 5, max 50)
sinceNoOnly plans generated on/after this date (ISO 8601, e.g. 2026-06-01)
offsetNoSkip this many results (default 0); use next_offset from the previous page

Output Schema

NameRequiredDescriptionDefault
countYesItems on this page
plansYes
totalYesTotal matching items
offsetYesItems skipped before this page
has_moreYesTrue when another page follows
next_offsetNoPass as offset to fetch the next page; absent on the last page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to repeat safety details. It adds meaningful behavioral context beyond annotations: ignored items are omitted, results are newest first and paginated, and each item includes angle, urgency, confidence, evidence, status, and a ~30-minute first step.

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?

The description is two sentences, front-loaded with the resource and scope, and every clause adds useful information. There is no filler or repetition of annotation or schema details.

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

Completeness5/5

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

An output schema exists, so the description is not required to explain return values in full, though it helpfully summarizes item fields. Combined with annotations and full parameter schema coverage, the definition gives an agent everything needed to call 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?

Schema coverage is 100%, so the baseline would be 3. The description adds semantic value by explaining that limit=1 retrieves just the current plan and by reinforcing the paginated, newest-first ordering, which goes beyond the schema's generic 'Max results per page' wording.

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?

The description opens with a specific verb and resource, 'List your weekly AI action plans', and immediately explains what those plans are: suggested action items generated from competitors' latest moves. This clearly distinguishes it from all sibling tools, which retrieve competitor data (battlecards, SEO, pricing changes, reviews, etc.) rather than your own action plans.

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?

The description provides useful usage guidance such as 'use limit 1 for just the current plan' and notes that ignored items are omitted. It does not explicitly frame when to choose this tool over siblings or when not to use it, but the resource distinction makes the intended context clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources