Skip to main content
Glama

streamfog_list_lenses

Read-only

List all available AR lenses and face filters from the local lenses.json mapping. Use reload=true to force a re-read from disk.

Instructions

List all available AR lenses and face filters from the local lenses.json mapping.

Returns all lens identifiers and their corresponding Streamer.bot action names. Use reload=true to force a re-read from disk if lenses.json was modified.

Return Format

{"success": true, "data": {"lenses": {"beauty_smooth": "SetLens_BeautySmooth", "cyber_helmet": "SetLens_CyberHelmet"}, "count": 2, "path": "lenses.json"}}

Examples

await streamfog_list_lenses() await streamfog_list_lenses(reload=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reloadNoIf true, reload the lens map from disk before listing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description adds behavioral details beyond readOnlyHint: the default cache behavior and the effect of reload=true. It also includes return format and examples, disclosing side effects.

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 efficient, using concise sentences and clear sections (Return Format, Examples). Every sentence adds value without redundancy.

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 simple list tool with one optional parameter, the description fully covers purpose, behavior, parameters, and return format. Examples further aid understanding.

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 coverage is 100%, so baseline is 3. The description adds context on when to use reload, but does not significantly extend the schema's description. Adequate.

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 lists all available AR lenses and face filters from a local file, with specific verb and resource. It distinguishes from siblings like streamfog_set_lens by being read-only.

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?

It explains when to use the reload parameter but does not explicitly contrast with other sibling tools. The context from sibling names makes the usage clear, but direct guidance is lacking.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/streamfog-mcp'

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