Skip to main content
Glama
Sign In
mesa-clm

mesa-clm

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ds_modify_access

Set access permissions for a user or group on a file or directory, optionally applying to all contents recursively.

Instructions

Modify data access of a user or group to a file (data-object) or directory (collection).

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": {
      "access_level": "<access_level>",
      "user_or_group": "<user_or_group>",
      "path": "<path>"
    },
    "name": "ds_modify_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe path to the file (data-object) or directory (collection) to modify access.
recurseNoIf set, apply the given access to all entries within the given directory (collection) recursively.
access_levelYesThe access level to set to the user. It can be 'own', 'delete_object', 'modify_object', 'create_object', 'delete_metadata', 'modify_metadata', 'create_metadata', 'read_object', 'read_metadata', or 'null'. For iRODS version prior to 4.3.0, only 'own', 'write', 'read', and 'null' are allowed.
user_or_groupYesThe user or group to set access. You can specify a user by 'username#zone' or a group by 'groupname#zone' to set zone. if zone is not specified, the client's zone will be used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that access is modified but does not mention required permissions (e.g., must be owner or admin), whether the access level replaces or adds to existing permissions, what happens to existing access, or any side effects or error conditions for this mutation operation.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and targets without unnecessary detail.

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?

For a mutation tool with no annotations, no output schema, and four parameters, the description is too sparse. It omits critical context such as required permissions, behavioral effects (replace vs. add access), and usage guidance, leaving significant gaps for an agent to invoke it correctly.

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%, so the schema already fully documents all four parameters including access levels, recursion, path, and user/group format. The description adds no additional meaning beyond what the schema provides, so the baseline score of 3 applies.

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 ('Modify') and resource ('data access') plus the targets ('a user or group to a file (data-object) or directory (collection)'). It clearly identifies what the tool does, though it does not explicitly distinguish itself from the sibling tool ds_modify_access_inheritance, which also deals with access-related modifications.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, no conditions for use, and no exclusions. It simply states the operation without any contextual usage information.

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

Deploy Server

Other Tools