Skip to main content
Glama
srgplus

srgplus-mcp

Official
by srgplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_permission_targets

Read-only

Retrieve all targets of a specified type in a workspace, including permission flags like edit and archive rights. Filter by parent or child type to narrow results.

Instructions

Get all targets of a given type accessible to the current user.

workspace_id: target workspace ID — get available IDs from list_workspaces()
target_type: "HubProfile", "Workspace", "Channel", etc.
child_target_type: filter to targets that have a child of this type
parent_target_id: filter to targets belonging to this parent
Returns each target with its permission flags (can_edit, can_archive, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_typeYes
workspace_idYes
parent_target_idNo
child_target_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.18

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already cover read-only and non-destructive behavior. The description adds relevant context about user accessibility and returned permission flags, but does not disclose potential side effects, auth requirements, or open-world implications beyond the annotation.

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 concise and well-structured: a one-sentence purpose followed by clear per-parameter explanations. No redundant or vague phrasing.

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?

With an output schema present, the description appropriately avoids detailing the return structure but still mentions permission flags. It is complete enough for the tool's simple purpose, though it lacks notes on pagination, ordering, or edge-case behavior.

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

Parameters5/5

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

All four parameters are explained in plain language, including examples for target_type and the filtering semantics of child_target_type and parent_target_id. This adds substantial meaning beyond the bare schema.

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?

Clearly states the verb ('Get'), the resource ('targets'), and the scope ('accessible to current user'). The description distinguishes it from sibling permission-checking tools (e.g., can_read, can_edit) by focusing on enumeration of targets.

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?

Provides useful parameter guidance and implies its use for listing accessible targets, but does not explicitly contrast it with alternatives or state when not to use it. Sibling tools like can_read and give_permission exist, but no direct comparison is made.

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