Skip to main content
Glama

pcprice.watch used PC part prices

list_tracked_models

Read-onlyIdempotent

The PC part models pcprice.watch tracks, with their IDs, optionally filtered by part type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
part_typeNooptional filter by part_type from list_tracked_models; omit to discover all currently tracked categories

Output Schema

NameRequiredDescriptionDefault
modelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / part_type / description
      Previous value: -"optional filter: GPU, CPU, RAM, MOTHERBOARD, PSU, LAPTOP, IPHONE"New value: +"optional filter by part_type from list_tracked_models; omit to discover all currently tracked categories"
  2. 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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that IDs are returned alongside models, hinting they can be used as keys for other tools, but it says nothing about result volume, ordering, or what happens for an unrecognized part_type.

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 front-loaded sentence that identifies the resource, the payload (IDs), and the optional filter with zero padding. It is perhaps slightly too terse to carry usage guidance, but nothing is wasted.

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 an output schema present, return values needn't be explained, and a single optional parameter keeps the tool simple. The description covers what is listed and the filtering option; only the relationship to sibling lookup tools is left implicit.

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 description coverage is 100%, so the single part_type parameter is already documented, including the advice to omit it to discover all categories. The description's "optionally filtered by part type" merely echoes the schema, adding no format or accepted-value detail.

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?

Names the specific resource (the PC part models pcprice.watch tracks) and states that IDs are returned, which is more than a restatement of the name. It doesn't explicitly contrast with check_ebay_listing or get_used_price, but those are clearly different operations, so an agent can still route correctly.

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 word "optionally" signals that the filter may be omitted, implying a discovery use case, but there is no explicit when-to-use or when-not-to-use guidance relative to siblings. Usage is only inferable from the filter's optionality.

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