Skip to main content
Glama

nexo_cortex_check

Validates reasoning before significant actions. Determines whether to act, propose, or ask to ensure appropriate next steps.

Instructions

Cognitive pre-action check. Validates reasoning and determines if you can act, should propose, or need to ask first. Call before significant actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesWhat you are trying to achieve (required)
task_typeNoOne of: answer, analyze, edit, execute, delegateanswer
planNoJSON array of planned steps (e.g. '["read file", "edit function", "test"]')[]
known_factsNoJSON array of facts you have (from user, memory, files)[]
unknownsNoJSON array of things you don't know yet but need[]
constraintsNoJSON array of rules or limitations that apply[]
evidence_refsNoJSON array of evidence supporting your plan (learnings, user statements, file contents)[]
verification_stepNoHow you will verify the action worked
Behavior2/5

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

No annotations are present, so the description alone must convey behavioral traits. It explains that the tool 'validates reasoning' and determines actionability, but does not disclose whether it is a read‑only operation, what side effects (if any) occur, or what permissions are needed. The description is too vague for full behavioral understanding.

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?

Extremely concise: two sentences, no redundant phrasing. The first sentence front‑loads the core identity ('cognitive pre‑action check'), and the second provides the essential usage directive. Every word earns its place.

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

Completeness2/5

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

Despite having 8 parameters and no output schema, the description omits crucial details: the output format (e.g., text, JSON), how the outcomes are communicated, and how parameters like 'verification_step' feed into the check. The agent lacks information to correctly interpret the response from this tool.

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%, with all 8 parameters having individual descriptions. The tool description itself adds no additional parameter meaning beyond the schema, so it meets the baseline of 3. The description could have clarified how parameters like 'plan' and 'unknowns' are used in the decision, but does not.

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?

Clear description of the tool as a 'cognitive pre-action check' that validates reasoning and yields one of three outcomes (act/propose/ask). This meaningfully differentiates it from sibling tools like nexo_confidence_check or nexo_guard_check, though it does not explicitly name alternatives.

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

Usage Guidelines3/5

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

States 'Call before significant actions' which gives a clear usage context. However, it does not specify when not to use it, nor does it mention alternative tools (e.g., nexo_pre_action_context) that might serve similar purposes in certain cases. The guidance is implied rather than explicit.

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/wazionapps/nexo'

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