Skip to main content
Glama

put_pvr_finished_id

Update properties of a finished recording, such as filename, state, or schedule, on your Freebox.

Instructions

Update a Frecord properties

Error codes: noent, inval, inval_date_fmt, inval_end_before_start, system_time_incorrect, record_duration_too_long, record_date_in_past, unknown_channel, no_channel_svc, only_auto_disable, cannot_change_en_state, cannot_disable_has_data, internal_error, none, file_access_error, disk_full, private_but_no_private_dir, network_problem, resource_problem, no_stream_available, no_data_received, missed, stopped, unknown_error

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id__pathYes(Path parameter)
idNofrecord id
mediaNomedia name on which the record is written. See the Media API for more info. This property and can be empty when the file backing the record is not available, for example when secure is set.
pathNodestination directory on the media storage
filenameNofilename of the record
byte_sizeNosize of the record file in bytes
has_record_genNoif true, this frecord has been generated using a Generator
record_gen_idNoif has_record_gen, this is the id of the generator
alteredNoan frecord is altered when some part of the recording may be missing. This can be the case if a conflict occurred during the recording (or connection was down)
stateNoValues: `disabled`: disabled; `start_error`: failed to start; `waiting_start_time`: scheduled; `starting`: starting; `running`: running; `running_error`: running with error; `failed`: failed; `finished`: finished
errorNo
channel_uuidNochannel uuid
channel_nameNooptional channel name
channel_qualityNo
channel_typeNoValues: `‘’ (empty string)`: auto; `iptv`: use only iptv streams; `dvb`: use only dvb streams
nameNorecord name
subnameNorecord subname
broadcast_typeNo
startNorecord start timestamp
endNorecord end timestamp
secureNoflag set when the record is protected by DRM

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It only states 'Update a Frecord properties' and lists error codes. It does not indicate whether the operation is destructive, requires authentication, or has 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.

Conciseness3/5

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

The main sentence is concise, but the extensive list of error codes bloats the description. A more structured format (e.g., bullet list or separate section) would improve readability.

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

Completeness2/5

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

With 21 parameters and complex error semantics, the description lacks context on what a Frecord is, prerequisites, or return behavior. The output schema exists but is not referenced, leaving the agent with gaps.

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 high (86%), providing descriptions for most parameters. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 'Update a Frecord properties' clearly states the action (update) and resource (Frecord properties). It distinguishes from siblings like put_pvr_programmed_id (updates programmed records) and get_pvr_finished_id (retrieves). However, 'Frecord' is jargon and could be clarified as 'finished PVR record'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like put_pvr_programmed_id or put_pvr_config. The error code list provides some conditions but does not direct the agent on selection based on context.

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/Nelson-PROIA/freebox-mcp'

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