Skip to main content
Glama
Sign In

Howseen

by ai.howseen
OverviewDiscussionsAdmin

Get the next action

get_next_action
Read-only

THE single most valuable next step for the brand, the same one the dashboard Overview shows (action engine, 20/80 ranking with the technical audit, Search Console and demand), with its steps, the questions it wins back and how to close it (which tool to call). Use it when the user asks "what should I do next?" or "what do I fix first?".

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD. Default: now.
fromNoStart date YYYY-MM-DD. Default: all time.
langNoLanguage of the texts (default en).
brandNoBrand id, name or domain (from list_brands). Optional when the account has a single brand.
engineNoOptional AI engine filter, comma separated: chatgpt, gemini, perplexity, ai_overviews, ai_mode. Default: all engines.

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?

Annotations already cover read-only, non-destructive and closed-world, so the safety profile is settled. The description adds genuine context beyond that: the 20/80 ranking method, the data sources feeding the rank, and the shape of the payload (steps, questions it wins back, how to close it). It does not discuss latency, caching, or what happens when no action qualifies.

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 claim is front-loaded in the opening clause and the usage trigger lands at the end, so an agent can skim it successfully. The middle is a dense stack of parentheticals and a capitalized "THE" that costs a little readability without adding much.

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 no output schema, the description carries the burden of explaining returns, and it does so by enumerating steps, questions won back, and the recommended closing tool. What is missing is any hint of the response envelope or what an agent should do if the returned action is already dismissed.

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 100% and all five parameters carry their own descriptions, including defaults and the brand-id source (list_brands), so the schema does the heavy lifting. The description adds nothing about how the date range or engine filter affect the ranking, leaving this at the baseline 3.

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 states a specific resource (the single top-ranked next action for a brand) and even names the ranking inputs (technical audit, Search Console, demand) and the dashboard parity. It is clear what the tool returns, but it never names or contrasts with siblings such as get_action_plan or get_easiest_wins, which sit close to it in the catalog.

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?

It gives concrete trigger phrasing ("what should I do next?", "what do I fix first?"), which is exactly the routing signal an agent needs. It stops short of stating when NOT to use it or which alternative to pick for a full prioritized list, so it earns a 4 rather than a 5.

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

All Howseen 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