Cortex MCP

Overview Schema Source Related Servers Discussions Admin

cortex_create_claim

Instructions

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": {
      "project_id": "<project_id>",
      "statement": "<statement>",
      "criteria": "<criteria>"
    },
    "name": "cortex_create_claim"
  }
}

Input Schema

Name	Required	Description	Default
`criteria`	Yes
`statement`	Yes
`project_id`	Yes

Output Schema

Name	Required	Description	Default
`status`	Yes
`claim_id`	Yes
`criteria`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

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 burden. 'Register' implies a mutating create, but the description does not disclose permission requirements, whether re-registering the same statement is rejected or duplicated, whether criteria are immutable after creation, or what happens on partial failure. For a write tool with zero annotation coverage, this leaves major behavioral questions unanswered.

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?

A single front-loaded sentence with no filler. Its brevity is efficient structurally, though it is under-specified rather than truly concise.

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?

An output schema exists, so return values need not be explained. However, with no annotations and an undocumented nested criteria object, the description does not give an agent enough to construct a valid, semantically correct criteria list or anticipate the tool's side effects.

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%, so all parameter meaning must come from the description. It loosely maps the three parameters ('claim' ~ statement, 'verification criteria' ~ criteria, 'in a project' ~ project_id), but says nothing about the criteria array's structure (key uniqueness, the 'required' boolean, the 1-32 item bounds) or length limits. This is a meaningful gap for the only non-scalar parameter.

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 (Register) and a specific resource (a claim and its verification criteria), scoped to a project. This distinguishes it from cortex_add_evidence and cortex_track_assumption by resource type, though the description never explicitly names those siblings.

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?

There is no guidance on when to register a claim versus tracking an assumption or adding evidence, nor any stated prerequisites (must the project exist first?). The only usage signal is the implied 'this is how you create a claim', which an agent must infer.

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

Deploy Server