Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pressable_get_account_details

Retrieve account profile and settings information for WordPress site management through the Pressable API.

Instructions

Retrieve account profile and settings information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools/account.js:8-10 (handler)
    The handler implementation for the pressable_get_account_details tool, which makes a GET request to the /account endpoint.
    handler: async () => {
    return await api.get('/account');
}
  • tools/account.js:4-11 (registration)
    The definition and registration of the pressable_get_account_details tool within the accountTools array.
    {
    name: 'pressable_get_account_details',
    description: 'Retrieve account profile and settings information.',
    inputSchema: { type: 'object', properties: {} },
    handler: async () => {
        return await api.get('/account');
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. 'Retrieve' indicates a read-only operation, but it does not disclose potential errors, response format, or authorization requirements, leaving behavior only partially transparent.

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 a single, concise sentence that front-loads the action and target. It contains no wasted words and is appropriately sized for the tool's simplicity.

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?

The tool is simple with no parameters or output schema, so the description covers the basic operation. However, it does not clarify what specific 'settings' are included or how this interacts with other account-level tools, leaving minor gaps in context.

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 input schema has zero parameters, so the baseline score is 4. The description adds no parameter details, but none are needed since the tool takes no arguments.

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 the tool retrieves 'account profile and settings information', with a specific verb and resource. This distinguishes it from sibling tools like activity logs and addons, making its purpose unambiguous.

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 description implies usage for account-level information but does not provide explicit when-to-use guidance or alternatives. It lacks exclusions, such as noting that site-specific details should use pressable_list_sites or pressable_get_site.

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