Skip to main content
Glama
Sign In
context-crystal

context-crystal

by oswaldo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

crystal_artifact

Register, list, inspect, or delete virtual and physical artifacts across cave or crystal registries to track targets, instruments, and preconditions by ID, URI, or location.

Instructions

Register, list, inspect, or delete virtual and physical artifacts across cave or crystal.

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": {
      "action": "<action>"
    },
    "name": "crystal_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoArtifact identifier (required for register/inspect/delete)
uriNoArtifact URI pointer
caveNoTarget cave registry
nameNoArtifact human-readable name
roleNoRole: target, instrument, or precondition
actionYesAction: list, register, inspect, delete, or remove
geo_uriNoGeo coordinates URI
substrateNoSubstrate: virtual or physical
crystal_idNoOptional crystal ID for crystal-scoped operations
media_typeNoMIME / media type
descriptionNoArtifact description
civic_addressNoPhysical civic address
location_nameNoPhysical location name
bench_coordinatesNoPhysical bench coordinates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • changedInput schema / properties / action / description
      Previous value: -"Action: list, register, or inspect"New value: +"Action: list, register, inspect, delete, or remove"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "register",
-  "inspect"
-]New value: +[
+  "list",
+  "register",
+  "inspect",
+  "delete",
+  "remove"
+]
    • changedInput schema / properties / id / description
      Previous value: -"Artifact identifier (required for register/inspect)"New value: +"Artifact identifier (required for register/inspect/delete)"
  2. First observedv0.1.0

TDQS

C2.9/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 of behavioral disclosure. It does not state that delete/remove are destructive, whether registration is idempotent, what permissions are required, or how cave and crystal registries differ beyond the brief scope phrase.

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 front-loaded sentence with no wasted wording. It is efficient, though its brevity leaves important action-specific behavior unaddressed for a 14-parameter tool.

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?

For a multi-action, 14-parameter tool with no annotations and no output schema, the description is materially incomplete. It does not explain which parameters apply to which action, what deletion does, or how cave versus crystal scope affects behavior.

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 parameter meanings are already well documented in the schema. The description adds only a small amount of context by mentioning virtual versus physical artifacts and cave/crystal scope, but it does not explain action-specific parameter requirements or the distinction between delete and remove.

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 gives concrete verbs and a resource: registering, listing, inspecting, or deleting artifacts, scoped across cave or crystal. It is more specific than a tautology, but it does not name or distinguish itself from sibling tools, and it omits the 'remove' action present in the schema.

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 lists operations but gives no guidance on when to choose this tool versus siblings such as crystal_search, crystal_archive, or crystal_prune. It also does not explain when to use cave versus crystal scoping, leaving usage to be inferred entirely from parameter names.

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