Fetch store details for the fixed PSA Team Store storefront, including normalized metadata. Use psastore_products or psastore_collections for catalog items, psastore_pages for page content, or psastore_sitemaps for sitemap discovery; no store URL is accepted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine context beyond that: the storefront is fixed (not user-selected), it returns normalized metadata, and no URL parameter is accepted, which prevents a common misuse.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action and resource, followed by a compact routing sentence. No filler; every clause carries routing or constraint information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists so return values need not be described, and annotations carry the safety profile. The description supplies the remaining essentials: what it fetches, its fixed scope, and how to reach the sibling tools instead.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, so the baseline is 4. The description reinforces this by stating 'no store URL is accepted', clarifying to the agent that it must not attempt to pass an identifier.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Fetch) and resource (store details) scoped to the fixed PSA Team Store storefront, and adds that normalized metadata is included. An agent can immediately distinguish it from the catalog/page/sitemap siblings by name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent to alternatives by task: psastore_products / psastore_collections for catalog items, psastore_pages for page content, psastore_sitemaps for discovery. It also states the negative constraint that no store URL is accepted.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
