Skip to main content
Glama
Sign In
whodb-cli

whodb-cli

Official
by clidey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

whodb_platform_next_actions

Read-onlyIdempotent

Returns deterministic suggested next actions for a selected hosted project, helping rank follow-up steps after a workspace summary or gap analysis.

Instructions

Return deterministic suggested next actions for the selected hosted project.

Use this as a deeper action-ranking view after whodb_platform_workspace_summary or whodb_platform_gap_analysis. Suggestions are advisory only; backend permissions and write confirmations still apply. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

NameRequiredDescriptionDefault
goalNoOptional user goal used to keep suggested actions relevant.
fieldsNoTop-level output fields to include, for example actions, warnings, goal.
workspaceNoOptional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.
omit_filesNoOmit root folder file and folder summaries. Defaults to false.
function_idNoFor runtime readiness, inspect the latest persisted run of this function without executing it.
omit_lineageNoOmit project lineage summary. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.136.0
    • addedInput schema / properties / function_id
      Added value: +{
+  "description": "For runtime readiness, inspect the latest persisted run of this function without executing it.",
+  "type": "string"
+}
  2. Addedv0.135.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, and the description adds real context on top: results are deterministic, advisory only, and backend permissions and write confirmations still apply. It also notes per-call workspace targeting does not change defaults, useful state-management detail. It does not describe the shape or size of the returned action list.

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?

Three tight sentences, front-loaded with the purpose before the sequencing and caveat. Every sentence carries information; only the workspace sentence duplicates schema content.

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 six parameters (including a nested workspace) and no output schema, the description should say more about what a 'suggested action' contains and how the fields/goal/function_id inputs shape that output. The sequencing and advisory caveats are covered, but the return-value burden falls entirely on an undocumented 'actions' concept.

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 description coverage is 100%, so the schema already documents goal, fields, function_id, omit_files and omit_lineage in detail. The description adds only the workspace-targeting semantics (per-call, defaults preserved), which largely restates the schema's own workspace description. Baseline 3 is correct here.

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?

States a specific verb and resource ('Return deterministic suggested next actions for the selected hosted project'), so the agent knows exactly what it produces. It is differentiated by sequencing from whodb_platform_workspace_summary and whodb_platform_gap_analysis, but never clarifies how it differs from near-name siblings like whodb_platform_pending or whodb_platform_action.

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 an explicit trigger and ordering: use it as a 'deeper action-ranking view after' two named siblings. The advisory-only caveat is also stated. There is no when-not guidance (e.g. when a shallower summary is enough), which keeps it below a 5.

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

Deploy Server

Other Tools