Skip to main content
Glama

Camera rules in Spain (AEPD)

camera_privacy_rules
Read-onlyIdempotent

What the Spanish Data Protection Agency (AEPD) allows for security cameras: inside a home, on the façade/garden/entrance (no public street beyond a minimal strip of the access, no neighbours, sign required, deletion within a month), in a community of owners, in a business, in an older person's home (AEPD guidance of June 2026) and in a tourist flat (no indoor cameras; decibel-only noise monitors). Returns the rule, key points and AEPD links.

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": "camera_privacy_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoWhere the camera goes: casa (inside the home), exterior (façade, garden, entrance, doorbell), comunidad (community of owners), negocio (business), mayores (older person's home), alquiler-turistico (tourist rental).
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
questionNoThe user's question, if the place is not clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds real substance beyond that: it discloses the response shape (rule, key points, AEPD links) and summarizes domain constraints such as sign requirements, one-month deletion, and the June 2026 guidance date for older persons' homes.

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?

It is a single very long sentence with a dense parenthetical list, which makes it harder to scan than it needs to be. The most important fact — what it returns — is buried at the end rather than front-loaded, and the enumerated scenarios could be bulleted or trimmed.

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 no output schema, the description correctly states the return contents, and it covers all six place scenarios plus two language options. A brief note on sourcing/authority limits or on how 'question' interacts with 'place' would make it fully complete, but nothing essential is missing for correct invocation.

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 description coverage is 100% and both enums are documented, so the schema does the heavy lifting. The description restates the place categories in prose and adds a little domain color (e.g. 'no indoor cameras; decibel-only noise monitors' for the tourist flat), but adds no new semantics for 'language' or 'question'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (AEPD camera privacy rules) and enumerates the six scenarios it covers, with an explicit statement of what it returns ('the rule, key points and AEPD links'). It does not explicitly differentiate itself from the sibling 'answer_library', but the scope is narrow and unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer it should be called for questions about security cameras in Spain. There is no explicit when-to-use/when-not statement, no mention of when to prefer answer_library or setup_guide, and no guidance on whether to call it once per place or once per question.

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.

Resources