package_searchFull-text + faceted search.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| fq | No | ||
| rows | No | ||
| sort | No | ||
| start | No | ||
| facet_field | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds only 'full-text + faceted search,' which does not disclose behavioral traits like pagination, rate limits, or result handling. It adds minimal context beyond the annotations.
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?
At three words, the description is extremely concise and free of fluff. However, it is under-specified for a tool with six parameters, making it concise at the expense of informativeness.
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?
Given the six-parameter schema with zero descriptions and no guidance in the description, agents cannot determine how to construct queries, what sort/facet options exist, or how pagination works. The output schema covers return values, but the description fails to compensate for the missing parameter semantics and usage context.
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?
Schema coverage is 0% and no parameter descriptions are provided. The phrase 'full-text + faceted' offers a weak hint that q maps to full-text and facet_field maps to faceted search, but rows, start, sort, and fq remain entirely unexplained. The examples in the schema show usage but not semantics.
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 identifies the tool as a search with full-text and faceted capabilities, but it does not explicitly state what is being searched (packages). This makes it distinct from a tautology but still vague about the resource and scope, especially compared to siblings like package_list or package_show.
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 guidance is given on when to use this tool versus alternatives such as package_list, package_show, or search_within. There is no mention of context, prerequisites, or exclusions, leaving agents to infer usage.
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.
Tools are generally distinct in purpose, but some overlap exists between ask_pipeworx, ask_pipeworx_grounded, and deep_research. Descriptions clearly differentiate them, but an agent might still need to carefully choose.
Most tool names follow a consistent snake_case pattern with clear prefixes (e.g., pipeworx_*, polymarket_*). A few names like compare_entities and validate_claim break the pattern, but overall it is predictable.
With 40 tools, the server is overly large for a single coherent set. Many tools are meta or auxiliary, but the count exceeds the 'too many' threshold, making it hard for agents to navigate.
The tool set covers data retrieval, Chilean open data, Polymarket, memory, and monitoring comprehensively. Minor gaps exist (e.g., no direct trading for Polymarket), but the surface is complete for the stated purpose.