Skip to main content
Glama

Trueprice

Store by brand name

find_store
Read-onlyIdempotent

Store domains for a brand or site name (e.g. "Nike", "allbirds"): with_codes = domains with promo codes a real cart accepted (count in working_codes; read them with store_codes), tracked_prices = domains whose product prices Trueprice reads daily (product count). Empty lists mean Trueprice doesn't cover that brand yet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "find_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBrand, store name or domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds genuine context the annotations do not: what each result bucket means and that empty lists signal the brand is not yet covered. It does not describe the response envelope beyond those two fields or how they behave for ambiguity in the name.

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?

One dense sentence, front-loaded with the verb and resource, with the two result buckets defined inline. The backtick-heavy inline notation is compact but readable; nothing is clearly redundant.

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?

With no output schema, the description carries the return-value burden and does so for the two documented lists including counts and the empty-list meaning. For a one-parameter lookup with rich annotations, that is nearly sufficient; missing only a note on what other fields (if any) accompany the two lists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% on the single required `name` parameter, so the baseline is 3. The description contributes example inputs ("Nike", "allbirds") that illustrate the accepted name/domain granularity, but adds no format or normalization rules beyond what the schema already says.

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 states a specific verb+resource: it resolves a brand/site name to store domains, and names the two result buckets (with_codes, tracked_prices). It is clearly distinguishable from store_codes, which it explicitly positions as the follow-up reader of codes. It stops short of stating what makes it different from search_products or find_products beyond the domain-vs-product axis.

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?

Usage is implied rather than stated: you supply a brand name and get domains back, and store_codes is named as the way to read the actual codes. There is no explicit when-to-use/when-not-to-use framing or guidance on choosing this over search_products or find_products for a starting-point lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources