Skip to main content
Glama
Sign In

Vari8ion

by com.vari8ion
OverviewDiscussionsAdmin

Set the technical drawings folder

set_drawings_folder
Idempotent

Record where the technical drawings folder is. It holds the drawings, their revisions and the drawing register. Optional. It helps Vari8ion find the files faster.

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": {
      "link_id": "<link_id>",
      "path": "<path>"
    },
    "name": "set_drawings_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAnything that helps find the files, such as a file naming rule.
pathYesThe folder path inside the shared folder, such as Project/01 Contract.
link_idYesThe link_id that start_project_link returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already disclose that this is a non-read-only, idempotent, non-destructive, closed-world operation. The description adds the optional speed benefit and clarifies the recorded folder's contents, but does not add detail about overwrite behavior or permission requirements beyond the 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?

The description is short and front-loads the core action. The extra sentences about folder contents and the speed benefit earn their place by adding context, though the fragment "Optional." is slightly choppy.

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 simple three-parameter setter with fully documented schema fields and clear annotations, the description covers purpose and optional benefit adequately. The main remaining gap is guidance on how this tool relates to the sibling folder setters.

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%, so the schema already documents link_id, path, and note. The description adds domain context about what the drawings folder contains, but does not add syntax or usage detail for the parameters beyond the schema.

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 states a specific verb and resource: "Record where the technical drawings folder is." It also clarifies what the folder contains, which makes the purpose concrete. It does not explicitly distinguish this tool from the sibling folder-setting tools.

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?

The description says the setting is optional and that it helps Vari8ion find files faster, which gives context for when to use it. However, it does not explicitly say when to choose this tool over sibling folder setters or when not to use it.

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

All Vari8ion toolsInspect
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