Schema | two-minds-one-lock

two-minds-one-lock

Describes the environment variables required to run the server.

Name	Required	Description
`TRACER_LOCK_LENGTH`	No	Lock code length (default likely 4).
`TRACER_LOCK_ALPHABET`	No	Alphabet of glyphs used in the lock.
`TRACER_LOCK_MAX_ATTEMPTS`	No	Maximum number of attempts before lockout.

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
observe_systemA	Read the lock before acting: the glyph alphabet, the code length, your remaining attempt budget, the diagnostics legend, and your probe history. Call this first -- it costs nothing.
probeA	Reconnaissance. Test a candidate code -- a string of glyphs from the alphabet, exactly code_length long. Returns ALIGNED (correct glyph in the correct slot) and DISPLACED (correct glyph in the wrong slot) counts. Costs one attempt. A probe NEVER opens the lock; it only gathers information. Probe to deduce the secret.
submit_solutionA	Commit to a final answer. Opens the lock if 'answer' is exactly the secret code; otherwise costs one attempt and returns only a rejection -- no diagnostics. Submitting before you have deduced the code wastes the budget. Probe first; submit once confident.
get_statusA	Lightweight check: attempts remaining, whether you are locked out, whether the lock is open, and how many probes/submits you have spent.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/presspausegarage/two-minds-one-lock'

If you have feedback or need assistance with the MCP directory API, please join our Discord server