Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_available_addons

Retrieve available add-ons for Pressable accounts to enhance WordPress site functionality and management capabilities.

Instructions

Get a list of available account add-ons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The definition and handler for 'pressable_get_available_addons' tool in tools/account.js.
        name: 'pressable_get_available_addons',
        description: 'Get a list of available account add-ons.',
        inputSchema: { type: 'object', properties: {} },
        handler: async () => {
            return await api.get('/account/add-ons/available');
        }
    },
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. States 'Get' implying read-only, but lacks critical behavioral details: return format, pagination, caching behavior, or what 'available' specifically means (purchasable vs. enabled). No indication of rate limits or auth requirements.

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?

Single sentence of appropriate length with no unnecessary words. Front-loaded with the action verb. However, brevity comes at the cost of omitting useful context about return values and sibling differentiation that could fit in a second sentence.

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?

Adequate for a zero-parameter read operation, but gaps remain: lacks output schema description (what fields define an add-on?), misses distinction from pressable_get_account_addons, and provides no behavioral constraints. Acceptable but minimal.

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?

Input schema contains zero parameters. According to evaluation rules, 0 parameters establishes a baseline score of 4. No additional parameter context is needed or provided.

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?

Description uses specific verb 'Get' and resource 'available account add-ons', clearly indicating a retrieval operation. However, it fails to distinguish from sibling tool 'pressable_get_account_addons', leaving ambiguity about whether this returns currently installed add-ons vs. add-ons available for purchase.

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?

Provides no guidance on when to use this tool versus alternatives, particularly the similarly named 'pressable_get_account_addons'. No mention of prerequisites, account requirements, or filtering capabilities.

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