Skip to main content
Glama
Sign In
organisation.md

organisation.md

by shashank-sn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_permissions

Read-only

Check if the current user has permission to perform actions like add, delete, approve, or merge, optionally against codeowners patterns for a specific file path.

Instructions

check if the current user can perform a specific action (add, delete, approve, merge).

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": {
      "action": "<action>"
    },
    "name": "check_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesthe action to check
pathNooptional file path to check permissions against codeowners pattern

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses the read-only nature consistent with annotations (readOnlyHint=true) and adds the context of specific actions. However, it does not explain return format or behavior on denial.

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, efficient sentence that communicates the core purpose without any wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool and good annotations, the description covers the main purpose but omits the optional path parameter and does not describe the result format.

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 description adds limited value. It mentions the actions from the enum but does not add meaning beyond the schema's parameter descriptions.

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?

The description clearly states the verb (check) and resource (permissions for the current user), and lists the specific actions (add, delete, approve, merge). This distinguishes it from siblings like check_roles.

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 implies the tool is used to check permissions for actions, but provides no explicit guidance on when to use versus alternatives like check_roles, nor any exclusions.

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