Skip to main content
Glama

保存全局默认权限

app_save_default_permissions

Saves the three global default permissions—file scope, command policy, and network policy—so you can apply consistent defaults across SideDesk sessions.

Instructions

UI 专用:保存三组全局默认权限胶囊(fileScope / commandPolicy / networkPolicy)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "app_save_default_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileScopeNo
commandPolicyNo
networkPolicyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description has to carry the full burden of behavioral disclosure. It does disclose the two behavioral facts that matter most: the scope is global or default (an app-wide effect, not a session-local one) and the tool is UI-facing. It does not say whether the save overwrites existing values, how omitted groups behave, or whether permissions or confirmation are required.

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 definition is a single front-loaded sentence: 'UI 专用' comes first, followed by the scope and the three fields, with no filler. It is taut and well ordered, though it is terse to the point of under-specification.

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 of global settings with no annotations, no output schema, and 0% schema description coverage, the definition leaves important questions open: whether the whole set is replaced or a partial save is possible, what the tool returns, and how it relates to the other app_save_* tools. The description is therefore not complete enough for an agent to call it with confidence.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should explain the parameters; instead it only restates their names as 'three permission capsules'. The enum values (read-only / shadow / direct, auto / disabled, allow / deny) carry some self-evident meaning, but 'shadow' and 'auto' need the description to explain them, and nothing is said about what happens when a parameter is omitted, even though none of the three parameters is required.

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 gives a specific verb (保存/save) and resource (三组全局默认权限胶囊) and enumerates the three permission groups (fileScope / commandPolicy / networkPolicy), so the agent can tell this apart from siblings such as app_save_draft or app_save_user_profile. It does not explicitly name a sibling it is not, which keeps it short of a 5.

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 prefix 'UI 专用' is a real usage cue: it signals this tool is for the UI rather than for an agent-driven call; that is close to a when-not condition. However, the description never says when an agent should call it instead of app_save_persona / app_save_user_profile / app_save_draft, nor what the prerequisites are, so the guidance stays implied.

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