Fetch storefront metadata for the PSA Team Store at store.psacard.com. Use it to retrieve store details without supplying a URL, since the endpoint is fixed.
Get PSA Store store metadata. Returns storefront metadata for the PSA Team Store (https://store.psacard.com). The storefront URL is fixed server-side, so no url parameter is accepted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses the fixed-URL constraint and confirms no url parameter exists, but says nothing about the shape/contents of the returned metadata, permissions, or caching behavior.
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?
Three short sentences, front-loaded with the purpose. Slight redundancy between 'store metadata' and 'storefront metadata', but nothing extraneous.
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?
For a zero-parameter, annotation-free tool with no output schema, the description covers what the tool returns (storefront metadata), the fixed target, and the absence of a url parameter. It stops short of describing the metadata fields, which would be the only remaining gap.
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?
The tool takes zero parameters, so the schema baseline is 4. The description adds a small amount of meaning by explaining why there is no url parameter (the storefront is fixed server-side).
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 and resource ('Get PSA Store store metadata') and names the concrete storefront URL, which pins down exactly which store is meant. It is distinguishable from the psastore_products/psastore_collections siblings, though it does not explicitly name them as alternatives.
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?
Usage is only implied: the description notes the storefront URL is fixed server-side and no url parameter is accepted, which hints at when this tool applies. It never states when to reach for this versus psastore_page, psastore_collections, or other psastore siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.