Skip to main content
Glama
imdeniil

ya-tracker-mcp

by imdeniil

update_queue_permissions

Update access permissions for a Yandex Tracker queue by providing payloads for read, grant, write, and create actions.

Instructions

Update queue access permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
readNoPermission payload for 'read' action
grantNoPermission payload for 'grant' action
writeNoPermission payload for 'write' action
createNoPermission payload for 'create' action (e.g. {"users": {"add": ["user1"]}})
queue_keyYesQueue key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description only states the action (update) without revealing behavioral traits. It doesn't state whether permissions are replaced or merged, whether it requires special authentication, or what side effects occur. Since no annotations exist, this is a significant gap.

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 description is a single concise sentence without fluff. However, it is under-specified for a tool with a complex permission model, so it's not appropriately sized.

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?

Given the complexity of permissions (multiple actions) and lack of annotations, the description is too brief to be complete. It doesn't explain the payload structure, default behavior, or what 'access permissions' entails.

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?

The schema descriptions cover all parameters with 100% coverage, providing basic descriptions for each. The tool description adds no extra meaning to the parameters, so baseline 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 uses a specific verb 'update' and resource 'queue access permissions', clearly indicating the tool's function. It doesn't explicitly distinguish from sibling tools like update_queue or get_queue_user_permissions, but the name and description are unambiguous enough.

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 vs alternatives. It doesn't mention that this is for modifying permissions as opposed to viewing them, or any prerequisites like being an admin.

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/imdeniil/ya-tracker-mcp'

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