Ignix

Attach a file to a task

add_agenda_file

Attach an image, video or audio that is already online (a public URL) to a task: role "reference" for what the agency sends (e.g. "film it like this"), "delivery" for a take the creator hands in. It is copied into that client library. Large takes are better uploaded by the person from the app (up to 5 GB).

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": {
      "id": "<id>",
      "url": "<url>",
      "type": "<type>"
    },
    "name": "add_agenda_file"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Task id (from list_agenda).
`url`	Yes	Public URL of the image, video or audio.
`name`	No	File name to show.
`role`	No	Default "reference".
`type`	Yes
`idempotencyKey`	No	Optional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare openWorldHint (external URL fetch) and destructiveHint=false; the description usefully adds that the file is copied into that client library, which is a real side effect an agent wouldn't infer. It omits permission requirements, what happens if the URL is unreachable, and any handling of duplicates, so it adds value but not a full behavioral picture.

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?

Front-loaded with the core action and constrained to essentially one dense sentence plus a size caveat. The nested parenthetical and the example quote add slight clutter but each clause carries information.

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?

For a 6-parameter mutation with no output schema, the description covers the operation's scope, side effect (copy into client library), the role distinction, and a size limit. Remaining gaps — failure behavior on bad URLs and permission requirements — are modest given the annotations already flag open-world and non-destructive behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so baseline is 3, but the description adds genuine semantics for the `role` enum: 'reference' is what the agency sends ('film it like this') and 'delivery' is a take the creator hands in. That business meaning is absent from the schema's bare enum and default value.

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?

States a specific verb+resource: attaching an image, video or audio file to a task. The parenthetical '(a public URL)' and the note that large takes are uploaded from the app distinguish it from upload-style siblings such as upload_media or import_media, though it never names an alternative explicitly.

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?

Gives a clear applicability condition — the media must already be online at a public URL — and routes oversized takes (up to 5 GB) away to the app-based upload path. It does not say what to do instead if the file is local, nor name a sibling tool to use in that case.

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

All Ignix 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?