Browse community-shared PC builds from meupc.net with title, price, and components. Sort by recent, top-rated, or new to find suitable configurations.
Builds de PC compartilhadas pela comunidade do meupc.net, com título, preço e componentes
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Número da página | |
| sort | No | Ordenação das builds ('melhores-recentes', 'melhores', 'novas') | melhores-recentes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as pagination behavior, rate limits, or what happens if no builds are found. The description only lists what is included in the builds, which is minimal.
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?
The description is a single sentence that conveys the essential purpose and content of the builds, with no unnecessary words. It is front-loaded and to the point.
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?
While the tool has only two parameters and no output schema, the description does not explain pagination or sorting behavior. It is adequate for a simple listing but could mention what each build entry contains beyond title, price, and components.
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 input schema has 100% coverage with descriptions for both parameters (sort and page). The description does not add any additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.
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?
The description clearly states that the tool lists PC builds shared by the community, including title, price, and components. This distinguishes it from sibling tools like get_build_details (likely for a single build) and component-related tools.
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?
No explicit when-to-use or when-not-to-use guidance is provided. Usage context is implied by the name and description, but there are no alternatives mentioned or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.