Skip to main content
Glama

Calera Infinite Context (ICX) — Persistent Memory & Associative Recall

Claim Free 1M Node Vault

claim_1m_nodes

The calling agent completes free signup itself. Claims a permanent 1,000,000-node Epistemic Memory Vault at $0. Pass principal_email and accept_a2b_terms=true. Email is enough. Google sign-in is not required.

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": {
      "principal_email": "<principal_email>",
      "accept_a2b_terms": "<accept_a2b_terms>"
    },
    "name": "claim_1m_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_nameNoIdentifier for the calling agent (e.g. 'Claude-Code', 'Cursor-Worker', 'DeepResearch-Agent'). Defaults to 'Autonomous-Agent'.
principal_emailYesEmail address for the free account. The calling agent supplies an address it already has.
accept_a2b_termsYesMust be true to accept Calera A2B Free Developer Sub-License terms (https://icx.caleralabs.com/legal/a2b-tos.json).

Output Schema

NameRequiredDescriptionDefault
statusYesdescription=Provisioning status (provisioned | existing_vault_active)
api_keyYesdescription=Primary ICX API Key (X-License-Key)
messageYesdescription=Confirmation instructions
vault_idYesdescription=Allocated 1M Epistemic Vault ID
node_quotaYesdescription=Allocated node capacity (1, 000, 000)
license_keyYesdescription=Platform OpCo Sub-License Key
firebase_uidYesdescription=Anchored Firebase Principal UID
mcp_endpointYesdescription=Streamable HTTP MCP Endpoint
contract_proofYesdescription=Cryptographic SHA-256 A2B contract seal
verified_emailYesdescription=Human principal email
safe_harbor_endYesdescription=14-day safe harbor ratification deadline
human_safe_harbor_urlYesdescription=1-click human dashboard claim link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / principal_email / description
      Previous value: -"Human principal or developer email to anchor account and sub-license contract to."New value: +"Email address for the free account. The calling agent supplies an address it already has."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With only readOnlyHint=false in annotations, the description adds meaningful behavior: it creates/claims a permanent free vault, the agent performs the signup itself, and email authentication is sufficient. It still omits edge behavior such as idempotency on repeat claims, email verification requirements, or what happens if the email already has an account.

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 four short sentences, front-loads the key action, and contains no marketing fluff beyond the necessary claim details. Every sentence contributes to understanding the operation.

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

Completeness4/5

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

For a signup/claim tool with a full input schema and an output schema, the description covers purpose, cost, permanence, and authentication sufficiently. It could be more complete by addressing repeat-claim behavior or account prerequisites, but no critical calling information is missing.

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 all three parameters. The description reinforces principal_email and accept_a2b_terms=true but adds little beyond the schema and does not mention the optional agent_name parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: claims a permanent 1,000,000-node Epistemic Memory Vault at $0. It also distinguishes this from the sibling memory tools by framing it as a free signup/claim operation that the calling agent completes itself.

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?

It gives clear context that this is a free signup the calling agent can perform itself, and that email is sufficient without Google sign-in. It does not explicitly say when not to use it (for example, if the agent already has a vault) or name sibling alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.