Skip to main content
Glama

add_local_camera

Add a camera feed to your local collection. Cameras persist across restarts and appear in searches with the 'local' source, ready to share upstream.

Instructions

Add a camera to your local collection. Local cameras persist in ~/.openeagleeye/local-cameras.json and survive restarts and registry updates. They appear in list_cameras and search_cameras with source 'local'. Share upstream anytime with submit_local.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable camera name
urlYesDirect image URL — must return JPEG or PNG on HTTP GET
cityYesCity name (e.g. 'London', 'New York', 'Sydney')
locationYesLocation description (e.g. 'Manhattan, New York, USA')
timezoneYesIANA timezone (e.g. 'America/New_York', 'Europe/London')
categoryNoCamera category
latNoLatitude of the camera
lngNoLongitude of the camera
auth_providerNoProvider name if API key is needed (e.g. 'Transport for London')
auth_signup_urlNoURL to register for API key
auth_key_requiredNoWhether the image URL requires an API key at fetch time
auth_key_typeNoHow to inject the key
auth_key_namesNoQuery param or header names for the key
auth_config_keyNoKey name to use in ~/.openeagleeye/config.json
auth_noteNoNotes about authentication
Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions persistence file and source label, but does not cover error scenarios like duplicate names or invalid URLs. Adequate but not thorough.

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?

Three sentences, all substantive and front-loaded with the core action. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 15 parameters and no output schema, the description is adequate but missing return value information. It explains persistence and source but could detail what the tool returns (e.g., success or camera ID).

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% with clear descriptions for all 15 parameters. The description adds no extra parameter detail; it notes category but not enum values. Meets baseline for high schema coverage.

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 explicitly states 'Add a camera to your local collection' with a specific verb and resource. It distinguishes from siblings like remove_local by detailing persistence and source.

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?

Provides clear context on when to use (adding persistent local cameras), describes behavior (survives restarts, appears with source 'local'), and references sibling tool submit_local for sharing. Does not explicitly state when not to use, but guidance is strong.

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/stuchapin909/Open-Eagle-Eye'

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