Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
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');
    }
},

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided (readOnlyHint, destructiveHint, etc.), so the description must carry the full burden of behavioral disclosure. While 'Retrieve' implies a read-only operation, the description lacks details about caching behavior, rate limiting, authentication scope, or what constitutes the 'account' context (e.g., authenticated user vs. organization).

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, efficient sentence with no redundant words. The action verb is front-loaded, and the structure appropriately reflects the simplicity of a zero-parameter getter tool.

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 the lack of output schema and annotations, the description adequately identifies the return domain (profile and settings) but leaves gaps regarding response structure, pagination (if any), or error conditions. Sufficient for simple tools but incomplete for robust integration.

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 contains zero parameters, establishing a baseline score of 4. The description correctly implies no filtering or input is needed by describing a direct retrieval of account information, aligning with the empty schema.

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 uses a specific verb ('Retrieve') and identifies the resource ('account profile and settings'). It distinguishes from site-specific siblings (e.g., pressable_get_site) by specifying 'account', but does not explicitly differentiate from other account-level tools like pressable_get_account_addons or pressable_get_account_activity_logs.

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, prerequisites such as authentication requirements, or any conditions where it should not be used. It states only what the tool does, not contextual usage patterns.

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