Skip to main content
Glama

Apply to the spatial-computing beta cohort (public)

ic_spatial_beta_apply

Submit an application to the 20-person spatial-computing beta. WRITES a real application under a real person's name and commits them to a 5-week in-person NDA-bound program, so CONFIRM EVERY ANSWER WITH YOUR HUMAN FIRST and never invent one on their behalf - particularly the NDA, commitment and in-person answers, which are promises they have to keep. Call ic_spatial_beta_program first for the catalog and the exact allowed values. One application per email address; a second is refused rather than silently merged. The response carries a claim_token shown EXACTLY ONCE: surface it to your human verbatim, because without it an applicant with no IC account can never read their own status again. No auth required; a token only attributes the application. Returns: { ok, application_id, claim_token, status, failed_gates, cohort, message }.

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": {
      "full_name": "<full_name>",
      "email": "<email>",
      "nda_ack": "<nda_ack>",
      "commit_5_weeks": "<commit_5_weeks>",
      "in_person_sf": "<in_person_sf>",
      "profile": "<profile>",
      "building_now": "<building_now>",
      "xr_experience": "<xr_experience>",
      "availability": "<availability>"
    },
    "name": "ic_spatial_beta_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail they actually read. Required.
handleNoTelegram or X handle. Optional.
nda_ackYesWill they sign the strict NDA before their first session? Required. A false is honest and is recorded as a failed gate rather than blocked.
profileYesExactly one of: AI founder | Prompt engineer | Computational designer | Vibe coder | Spatial UI/UX tinkerer | XR developer | Researcher | Other. Required.
full_nameYesApplicant's full name. Required.
heard_viaNoHow they heard about it. Optional.
availabilityYesExactly one of: Weekday daytime | Weekday evenings | Weekends | Flexible / most times. Required.
building_nowYesWhat they are building right now, in their own words. Required.
in_person_sfYesCan they get to Frontier Tower, San Francisco in person regularly? Required. The hardware never leaves the building.
project_linkNohttps URL to a project, GitHub or portfolio. Optional.
accessibilityNoAccess needs or anything affecting headset use. Optional, accommodated, never used to screen anyone out.
anything_elseNoAnything else. Optional.
xr_experienceYesExactly one of: None - total newcomer | Tried a few times | Regular user | I build for headsets. Required. Newcomers are WANTED - do not inflate this to make an application look stronger.
commit_5_weeksYesCan they commit to the full 5 weeks? Required.

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and idempotentHint=false; the description goes far beyond by explaining that a real person's name is committed to a 5-week in-person NDA program, that duplicate emails are refused rather than merged, that no auth is needed, and that a `claim_token` is returned exactly once and permanently gates future status reads. That last point is a genuine behavioral trap an agent would otherwise miss. Consistent with annotations: WRITES matches readOnlyHint=false, and nothing claims idempotency.

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?

Dense but front-loaded — the write-and-commit warning comes first and the return shape last. Every clause carries operational weight (confirm-with-human, dedupe rule, claim_token). It runs long in a single unbroken block, and splitting the claim_token handling into its own line would read faster, but nothing is filler.

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

Completeness5/5

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

For a 14-parameter, 9-required mutation with real-world consequences, the description covers the write semantics, the ordering dependency on a sibling tool, the one-per-email constraint, the token handling that the output schema cannot express, and the return envelope. Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning on top: it flags the NDA, commitment and in-person booleans as promises the applicant must keep, and instructs the agent to confirm every answer with the human and never invent one. It also routes enum values to ic_spatial_beta_program for the exact allowed set, which the schema lists inline but the description guards against fabrication.

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?

Opens with a specific verb+resource ("Submit an application to the 20-person spatial-computing beta") and immediately names the scope: 20 seats, 5-week in-person NDA-bound cohort. It also distinguishes itself from the sibling read tools by pointing to ic_spatial_beta_program for the catalog and by describing ic_spatial_beta_status's audience (applicants with no IC account).

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

Usage Guidelines5/5

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

Gives explicit prerequisites ("Call ic_spatial_beta_program first for the catalog and the exact allowed values") and an explicit exclusionary rule ("One application per email address; a second is refused rather than silently merged"). It also states the human-in-the-loop condition as a hard requirement before calling, which is the key when-to-use gate for this tool.

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.