agent-media

set_location

Destructive

Paid replacement of a location plate (index 0 to 2 on older series, 0 to 7 on cast v2 with optional name, setting interior|exterior, time day|dusk|night; at most 2 replacements per location). Existing jobs retain their locked location references.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "series_id": "<series_id>",
      "index": "<index>",
      "description": "<description>"
    },
    "name": "set_location"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`time`	No
`index`	Yes
`dry_run`	No
`setting`	No
`series_id`	Yes
`description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026

addedInput schema / properties / dry_run

Added value: +{
+  "default": false,
+  "title": "Dry Run",
+  "type": "boolean"
+}

addedInput schema / properties / name

Added value: +{
+  "default": "",
+  "title": "Name",
+  "type": "string"
+}

addedInput schema / properties / setting

Added value: +{
+  "default": "",
+  "title": "Setting",
+  "type": "string"
+}

addedInput schema / properties / time

Added value: +{
+  "default": "",
+  "title": "Time",
+  "type": "string"
+}

AddedOct 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already flag it as destructive and open-world, and the description adds valuable context: it is a paid operation, limited to at most 2 replacements per location, and existing jobs retain locked references. Missing details like exact cost or permission requirements, but solid beyond annotations.

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

Conciseness4/5

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

One dense but front-loaded sentence with no wasted words; the key action and cost are stated first, followed by constraints and parameter cues. Slightly packed but still readable.

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?

Given a destructive, paid mutation with no output schema and 0% schema description coverage, the description covers cost, limits, index ranges, allowed values, and effect on existing jobs. Missing explicit links to sibling tools and some parameter details, but largely complete.

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 0%, so the description must carry the load. It explains index ranges, setting values, time values, and optional name, but omits series_id, description, and dry_run entirely. Partial compensation for the coverage gap.

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 specific verb ('replacement') and resource ('location plate') with cost and scope details. Implicitly distinguishes from sibling 'add_location' by being a replacement rather than an addition, and from other mutating tools by focusing on a single plate.

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?

Implies usage through the 'Paid replacement' framing and constraints, but never explicitly says when to choose this over alternatives like add_location or recast. No when-not guidance is provided.

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

All agent-media tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?