Skip to main content
Glama
Sign In
mcp-server-osascript

mcp-server-osascript

by FradSer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_security_profiles

Retrieve all security profiles with patterns, risk levels, and usage recommendations to configure secure AppleScript execution.

Instructions

    Get information about all available security profiles.

    Returns detailed information about each security profile including their
    patterns, risk levels, and usage recommendations.

    Returns:
        Dictionary with security profile information and current configuration

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": "get_security_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. The verb 'get' implies a read-only operation, and the mention of 'Returns' indicates no side effects, but there is no explicit statement about permissions, side effects, or data freshness. This is adequate but lacks the richness seen in well-disclosed tools.

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 three sentences: the first gives the main purpose, the second elaborates on the content, and the third states the return type. Every sentence earns its place without redundancy, and the key purpose is front-loaded in the first sentence.

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

Completeness5/5

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

Given that this is a simple zero-parameter getter with an output schema present, the description is complete. It covers what the tool does and what it returns, and the lack of usage guidance is not a completeness gap for such a straightforward operation. The output schema already provides structural detail.

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

Parameters4/5

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

The tool has zero parameters and the schema provides 100% coverage (empty object). With 0 params, the baseline is 4. The description correctly adds no parameter details because there are none, and the return description is sufficient for the tool's purpose.

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 'Get information about all available security profiles' with a specific verb (get) and resource (security profiles). It distinguishes itself from the sibling tool set_security_profile by focusing on retrieval rather than modification, and the scope 'all available' is clear.

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. It does not mention set_security_profile or any conditions under which this getter should be invoked, such as before setting a profile. The agent must infer usage solely from the tool name and sibling names.

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