Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_account_addons

Retrieve a list of add-ons attached to your WordPress hosting account to manage and monitor available features.

Instructions

Get a list of add-ons attached to your account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for pressable_get_account_addons, which makes an API request to /account/add-ons.
        name: 'pressable_get_account_addons',
        description: 'Get a list of add-ons attached to your account.',
        inputSchema: { type: 'object', properties: {} },
        handler: async () => {
            return await api.get('/account/add-ons');
        }
    }
Behavior2/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 behavioral disclosure. It states the operation reads data but doesn't mention if it's read-only safe, whether there are rate limits, authentication requirements, or what the response structure looks like. 'Get a list' is minimally descriptive of the operation's nature.

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 description is extremely concise at 9 words with no redundant or wasteful content. The key information is front-loaded ('Get a list'). However, given the lack of annotations and output schema, the extreme brevity means it fails to add contextual value that could have been included within a reasonable length.

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 this is a simple parameter-less read operation, the description is minimally viable. However, it lacks important contextual distinction from the sibling 'pressable_get_available_addons' tool and provides no insight into the response format, making it barely adequate rather than complete.

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 0 parameters, which per the scoring guidelines establishes a baseline of 4. There are no parameters requiring semantic clarification beyond what the (empty) schema provides.

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 states a clear verb ('Get') and resource ('add-ons'), with scope clarification ('attached to your account'). This implicitly distinguishes from the sibling tool 'pressable_get_available_addons' by using 'attached' versus 'available', though it doesn't explicitly name the sibling for differentiation.

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 explicit guidance on when to use this tool versus alternatives, prerequisites, or when NOT to use it. While the purpose is clear enough to imply usage (when you need to see current add-ons), there is no explicit 'when-to-use' guidance.

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/PCWProps/pressable-mcp-server'

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