Skip to main content
Glama

Get my recommended actions

get_actions
Read-onlyIdempotent

Kliqo's recommended actions for the project (suggested automatically from the data, or added by the team), most important first: what to do, why, the steps, the page to change and the expected impact. Pass action_id for one action's details and evidence. Use for "what should we do to show up in ChatGPT?" or when planning work; in a code editor, an action's steps can be applied to the site. Needs sign-in to Kliqo (read-only).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoopen = suggested, to do and in progressopen
projectNoProject name, domain or id; leave out for the workspace's current project
action_idNo

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's job is lighter. It still adds useful context beyond them: the sign-in requirement, the read-only nature, and the ordering guarantee ('most important first'). It does not mention pagination beyond the limit cap or any failure behavior.

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?

The core purpose and result content are front-loaded, and the action_id detail mode follows. The long opening clause packing five returned fields is dense, but every element conveys real information and nothing is wasted.

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 rich annotations, the description covers what the agent needs: content of results, default ordering, detail mode, and auth. Only minor gaps remain around how the four params interact (e.g., whether limit applies in action_id mode).

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 coverage is 50%, and the description only explains action_id (returns one action's details and evidence), which the schema leaves undocumented. The status enum, limit, and project parameters get no added meaning in the description beyond the existing schema text for project and status.

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 verb and resource (recommended actions for the project) plus the returned content: what to do, why, steps, target page, expected impact. It also distinguishes a list mode from a single-action detail mode via action_id, so an agent can tell what it will get.

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?

Gives concrete use cases ('what should we do to show up in ChatGPT?', planning work, applying steps in a code editor) that map to realistic agent intents. It does not name alternatives such as get_fix_plan or get_briefing, nor state when not to use it, so sibling routing is left to inference.

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