Skip to main content
Glama

seshat_get_next_action

Read-onlyIdempotent

Identify the single next permitted action in a governed BI pipeline and check if an intended action is allowed before starting.

Instructions

Return the one action readiness allows now, and refuse anything past it.

Use when: you need the single permitted next step, or want to check an intended action is allowed before starting it. Not for: the full stage picture (use seshat_get_status) or blocker detail (use seshat_explain_blockers). Returns: one allowed action plus forbidden scope, the stop point and the authority required to go further. Outcome is 'blocked' when requested_scope is forbidden or a named-human decision is outstanding. Read-only: names the action but never performs it, and grants no approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableNoSingle table to scope the answer to, matching a table name or its mapping directory (for example 'retail_store_sales'). Omit to cover every onboarded table in the workspace. May not contain '/', '\' or '..'.
workspaceYesPath to the local Seshat BI workspace to read. Must resolve to exactly the root this server was started with; a parent or subdirectory is refused.
requested_scopeNoPlain-text action you intend to take, checked against what readiness currently forbids; words longer than three characters are matched, and a collision returns outcome 'blocked' instead of an allowed action. Omit to simply read the allowed action.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description states 'Read-only: names the action but never performs it, and grants no approval,' adding context beyond the readOnlyHint and idempotentHint annotations. It also reveals the 'blocked' outcome condition, which is useful behavioral information.

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 structured with clear sections (Use when, Not for, Returns, Read-only) and every sentence provides distinct value. It is appropriately sized with no redundant information.

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?

Given the output schema exists, the description still provides key behavioral details, return format, and exclusions. It covers the tool's purpose, usage, limitations, and side effects (none), making it fully complete for an agent to decide when and how to invoke it.

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?

The input schema already provides 100% description coverage for all parameters, including detailed semantics for requested_scope. The description adds the high-level use case of checking an intended action but no parameter-specific details beyond the schema. Baseline 3 is appropriate.

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 'Return the one action readiness allows now, and refuse anything past it,' which is a specific verb+resource statement that clearly conveys the tool's function. It also distinguishes from siblings by naming seshat_get_status and seshat_explain_blockers as alternatives.

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

Usage Guidelines5/5

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

The description explicitly provides a 'Use when' section and a 'Not for' section with named sibling tools, giving clear guidance on when to use this tool versus alternatives. It also mentions checking an intended action, which is a key use case.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kemetra/Seshat-BI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server