Skip to main content
Glama
Sign In
Cortex Intelligent

Cortex Intelligent

by adyoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

self_critique

Evaluates an artifact against a weighted checklist, returning scores, severity ratings, and a verdict to guide structured self-review without an LLM.

Instructions

Structured self-critique (weighted checklist + scoring + severity + verdict) without LLM.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artifact": "<artifact>"
    },
    "name": "self_critique"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNo
artifactYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / tier
      Added value: +{
+  "enum": [
+    "weak",
+    "medium",
+    "strong"
+  ],
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the tool works 'without LLM' and names output components, but it does not explain how scoring is performed, what severity thresholds mean, whether the artifact is modified, or what the result format looks like.

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 description is a single compact sentence with no wasted language and is front-loaded with the core purpose. However, its extreme terseness contributes to the missing usage and parameter details.

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?

Given that there are no annotations, no output schema, and 0% schema description coverage, the description is too sparse for a tool with a non-trivial scoring and verdict model. It names the artifact and tier parameters nowhere, leaving the agent unable to confidently call the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention either parameter. The meaning of 'artifact' is only weakly implied, and the role of the 'tier' enum (weak/medium/strong) is not explained at all.

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 that the tool produces a structured self-critique with weighted checklist, scoring, severity, and verdict, and that it operates without an LLM. This is more specific than the bare tool name, but it does not distinguish the tool from related siblings such as score_compliance or run_verification.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. An agent must infer usage from the phrase 'self-critique' alone.

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