lens

Create a Mindola lens

create_digital_twin_lens

Create a shareable Mindola lens (AI clone) from a profile the user has approved in this conversation. Call this only after summarizing the proposed lens for the user and receiving explicit confirmation. Use only information the user provided or confirmed in the conversation; do not claim access to hidden memory, private chats, or external accounts.

Input Schema

TableJSON Schema

Name	Required	Description
`bio`	No	A concise first-person or third-person biography assembled from user-confirmed information.
`tone`	No	The visitor-facing tone of the lens.
`facts`	No	Concrete user-approved facts to seed the lens memory. Each item should stand alone.
`locale`	No	Optional BCP-47 locale for user-facing lens copy.
`context`	No	Extra grounding context for how the lens should answer. Use only information the user confirmed.
`tagline`	No	A short one-line summary of what this lens represents.
`audience`	No	Who this lens is intended to help or answer questions for.
`expertise`	No	Specific domains, skills, or interests the user confirmed.
`topicName`	No	The Mindola space name that will hold the seeded facts.
`vibeWords`	No	Up to four short adjectives for the lens profile.
`boundaries`	No	Things the lens should not claim, discuss, or answer beyond. Ask the user to confirm these before calling.
`accentColor`	No	Optional hex color, for example #4f46e5.
`displayName`	No	The user's preferred public name for the lens, after they confirm it.
`sourceSummary`	No	Short note describing what ChatGPT used to assemble the profile, without exposing hidden chain-of-thought or unapproved private data.
`suggestedPrompts`	No	Starter questions visitors can ask the lens.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`claimUrl`	Yes
`shareUrl`	Yes
`expiresAt`	Yes
`factCount`	Yes
`manageUrl`	Yes
`topicName`	Yes
`displayName`	Yes
`claimRequired`	Yes
`suggestedPrompts`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive nature. The description adds valuable context about needing explicit user confirmation, using only user-approved information, and avoiding claims of access to hidden memory or private data. No contradiction with annotations.

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 two sentences long, front-loaded with the purpose, and every word adds value. It succinctly conveys the action, the precondition, and the information-source constraint without repetition.

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?

Given the complete parameter schema and the presence of an output schema, the description sufficiently covers the essential context: creation of a new lens, the confirmation gate, and data provenance. It could mention more about post-creation effects, but these are likely covered by the output schema.

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?

The input schema provides 100% description coverage for all 15 parameters with detailed descriptions. The tool description adds overall context about assembling the profile from user-confirmed info but does not add parameter-specific meaning beyond what the schema already provides.

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 clearly states the tool creates a shareable Mindola lens (AI clone) from an approved profile, using the specific verb 'Create' and the resource 'Mindola lens'. This distinguishes it from siblings like add_lens_knowledge and get_lens_status.

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?

The description explicitly says to call only after summarizing the lens and receiving explicit confirmation, providing a clear precondition. It also restricts information to user-provided content, but does not explicitly name alternatives or exclusions beyond the confirmation requirement.

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

All lens tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool performs a distinct action: creating a lens, adding knowledge, and checking status. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool for a given task.

Naming Consistency5/5

All tool names follow a strict verb_noun pattern (add, create, get) with clear object nouns (lens_knowledge, digital_twin_lens, lens_status). This consistency makes the naming predictable and easy to understand.

Tool Count5/5

With only 3 tools, the set is perfectly scoped for the focused purpose of managing Mindola lens creation and monitoring. The count is not excessive, and each tool serves a necessary function without unnecessary redundancy.

Completeness5/5

The tools cover the full workflow: create a lens, add knowledge to it, and check its status. There are no obvious missing operations for the stated domain, and the workflow is complete without dead ends.

Create a Mindola lens

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources