Skip to main content
Glama

nexo_cortex_check

Validate reasoning before significant actions. Determines if you can act, should propose, or need to ask first based on goal and context.

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
Behavior3/5

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

With no annotations, the description must cover behavioral traits. It explains that the tool validates reasoning and returns a decision (act/propose/ask), which is helpful. However, it does not disclose side effects, authentication needs, rate limits, or whether it stores data, leaving some gaps.

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 two sentences long, front-loaded with the core purpose, and contains no redundant information. Every word earns its place.

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?

Given the 8 parameters, no output schema, and no annotations, the description is adequate but incomplete. It explains the tool's role but does not describe the return format or how the validation outcomes are structured, which would help an agent fully utilize the response.

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%, with each parameter well-documented (goal, task_type, plan, etc.). The description adds no additional meaning beyond summarizing the tool's purpose. Baseline 3 is appropriate as the schema already provides sufficient detail.

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 clearly states it is a cognitive pre-action check that validates reasoning and determines if you can act, propose, or ask. It distinguishes itself from other check tools (e.g., guard_check, confidence_check) by focusing on reasoning validation before significant actions, though it could be slightly more specific about outputs.

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?

The description advises calling 'before significant actions,' providing clear timing guidance. However, it does not mention when not to use this tool, nor does it reference alternatives among the many sibling check tools (e.g., nexo_guard_check, nexo_confidence_check).

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