Skip to main content
Glama

Simulate Eye Condition or Visual Symptoms

simulate_vision
Read-onlyIdempotent

Renders an interactive first-person vision simulation (featuring a child-friendly near dog, midground streetlamp, and far mountains) directly in chat and generates shareable ArkSight deep links. Especially helpful when parents, teachers, or clinicians want to help a child express or show what they are seeing, as well as for adults exploring visual symptoms or what any of 26 eye conditions look like (e.g., cataracts, AMD, glaucoma, uveitis, astigmatism, myopia, retinal detachment, keratoconus, floaters, visual snow). Valid preset IDs: myopia, hyperopia, presbyopia, astigmatism, cataracts, uveitis, keratoconus, dry-eye, fuchs-dystrophy, keratitis, amd, diabetic-retinopathy, retinal-detachment, pvd, epiretinal-membrane, retinitis-pigmentosa, cscr, macular-hole, stargardt, retinal-vein-occlusion, glaucoma, optic-neuritis, diplopia, hemianopia, ocular-migraine, visual-snow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "simulate_vision"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNoOptional eye condition preset slug (myopia, hyperopia, presbyopia, astigmatism, cataracts, uveitis, keratoconus, dry-eye, fuchs-dystrophy, keratitis, amd, diabetic-retinopathy, retinal-detachment, pvd, epiretinal-membrane, retinitis-pigmentosa, cscr, macular-hole, stargardt, retinal-vein-occlusion, glaucoma, optic-neuritis, diplopia, hemianopia, ocular-migraine, visual-snow). Can be combined with individual symptom overrides.
blurFarNoDistance blur on the background mountains while foreground dog stays sharp (0 to 10; myopia).
blurNearNoNear-field blur on the foreground dog while distant mountains stay clear (0 to 10; hyperopia/presbyopia).
floatersNoDrifting dark specks, cobwebs, and rings % (0 to 100; PVD, retinal detachment, diabetic retinopathy, uveitis).
brightnessNoOverall light brightness % (100 = normal, lower = night blindness or optic dimming).
cloudyHazeNoCloudy, milky lens or corneal haze washing out contrast % (0 to 100; cataracts, uveitis, Fuchs', keratitis).
glareHalosNoLuminous halos and starburst glare around the streetlamp % (0 to 100).
visualSnowNoFine grainy TV-like static across the visual field % (0 to 100; visual snow syndrome).
blurOverallNoOverall blur across near, mid, and far distances (0 to 10).
floaterSizeNoFloater size modifier when floaters > 0 (1 to 20, default 10).
kidFriendlyNoSet true when simulating for a child or parent to enable child-friendly symptom wording.
doubleVisionNoGhosting / overlapping double vision intensity % (0 to 100; diplopia, keratoconus, astigmatism).
lightFlashesNoPeripheral arcs or flickers of light / photopsia % (0 to 100; PVD, retinal tear/detachment, ocular migraine).
tunnelVisionNoConcentric peripheral narrowing / tunnel vision % (0 to 100; glaucoma, retinitis pigmentosa).
curtainShadowNoDark curtain sweeping across vision % (0 to 100; urgent retinal detachment warning sign).
wavyDistortionNoMetamorphopsia wavy distortion bending straight lines like the streetlamp pole (0 to 50; AMD, macular pucker/hole, CSCR).
centralDarkSpotNoCentral scotoma / dark smudge at the center of gaze % (0 to 100; AMD, macular hole, Stargardt, optic neuritis).
compareWithNormalNoSet true to open side-by-side comparison against clear reference sight.
missingPatchesGridNo16-character row-major 4x4 bitmask of missing field patches ('1' = blind patch, '0' = clear; e.g. '0011001100110011' for right hemianopia).

Output Schema

NameRequiredDescriptionDefault
presetYes
urgentYes
summaryYes
clinicPdfUrlYes
simulatorUrlYes
conditionNameYes
simulatorStateYes
urgentWarningsYes
conditionPageUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / affectedEye
      Removed value: -{
      -  "description": "Which eye is affected ('both', 'left', or 'right').",
      -  "enum": [
      -    "both",
      -    "left",
      -    "right"
      -  ],
      -  "type": "string"
      -}
    • removedOutput schema / properties / affectedEye
      Removed value: -{
      -  "enum": [
      -    "both",
      -    "left",
      -    "right"
      -  ],
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "preset",
      -  "conditionName",
      -  "summary",
      -  "affectedEye",
      -  "urgent",
      -  "urgentWarnings",
      -  "simulatorState",
      -  "simulatorUrl",
      -  "conditionPageUrl",
      -  "clinicPdfUrl"
      -]New value: +[
      +  "preset",
      +  "conditionName",
      +  "summary",
      +  "urgent",
      +  "urgentWarnings",
      +  "simulatorState",
      +  "simulatorUrl",
      +  "conditionPageUrl",
      +  "clinicPdfUrl"
      +]
  2. Changed5 schema fields changed
    • addedInput schema / properties / affectedEye
      Added value: +{
      +  "description": "Which eye is affected ('both', 'left', or 'right').",
      +  "enum": [
      +    "both",
      +    "left",
      +    "right"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / kidFriendly
      Added value: +{
      +  "description": "Set true when simulating for a child or parent to enable child-friendly symptom wording.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / affectedEye
      Added value: +{
      +  "enum": [
      +    "both",
      +    "left",
      +    "right"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / conditionPageUrl
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "preset",
      -  "conditionName",
      -  "summary",
      -  "urgent",
      -  "urgentWarnings",
      -  "simulatorState",
      -  "simulatorUrl",
      -  "clinicPdfUrl"
      -]New value: +[
      +  "preset",
      +  "conditionName",
      +  "summary",
      +  "affectedEye",
      +  "urgent",
      +  "urgentWarnings",
      +  "simulatorState",
      +  "simulatorUrl",
      +  "conditionPageUrl",
      +  "clinicPdfUrl"
      +]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description usefully adds that output is rendered in chat plus shareable deep links. It does not mention whether presets can be combined with overrides in conflicting ways, any rate or size limits, or that the simulation is illustrative rather than diagnostic — the latter being a meaningful omission for a health-adjacent tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The capability statement is front-loaded appropriately, but the 26-item preset enumeration is repeated verbatim from the input schema, consuming a large share of the text without adding information. The long parenthetical condition list inside the first sentence also hurts readability.

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?

With 19 optional parameters, an output schema, and full annotation coverage, the description supplies the necessary scene context, audience framing, and preset vocabulary for an agent to call it correctly. The main remaining gap is guidance on interpreting or combining parameters and any caveat about simulation fidelity.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds value by enumerating the valid preset IDs and noting presets can be combined with symptom overrides. It still duplicates the preset list already in the schema and does not explain interaction between preset and override parameters.

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?

States a concrete verb and output ('Renders an interactive first-person vision simulation... directly in chat and generates shareable ArkSight deep links') plus the specific scene contents and the 26 supported condition presets. It is clearly distinguishable from siblings like assess_visual_symptoms and list_eye_conditions, which do not render anything.

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?

Gives concrete audiences and situations: parents/teachers/clinicians helping a child express what they see, and adults exploring symptoms or condition appearance. It does not explicitly say when to prefer assess_visual_symptoms or list_eye_conditions instead, so it stops short of full routing guidance.

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.