List PyLops operator names, optionally filtered by module and version, to quickly find available operators for your computational tasks.
List operator names, optionally filtered by module (e.g. "basicoperators").
pylops_version selects the PyLops version (e.g. "2.6"); default is the latest.
| Name | Required | Description | Default |
|---|---|---|---|
| module | No | ||
| pylops_version | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that pylops_version defaults to the latest, which is useful behavioral context, but it does not mention pagination, permissions, or other operational details beyond the basic listing 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?
The description is two short sentences with no wasted content. The primary purpose is front-loaded, and parameter details follow immediately.
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 low-complexity list tool with an output schema, the description covers purpose, both parameters, and the version default. It could be slightly more complete by noting how this relates to sibling discovery tools, but the essential information is present.
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?
Although schema description coverage is 0%, the description compensates by explaining both parameters: module is an optional filter with an example, and pylops_version selects the version with a default. It does not enumerate valid module names, but both parameters are meaningfully explained.
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 states a specific verb and resource: listing operator names, with an optional module filter and version selector. It is clearly distinct from siblings like get_operator, though it does not explicitly contrast with list_proxoperators.
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 implied by 'List operator names' and the optional module filter, but there is no explicit guidance on when to use this versus alternatives such as search or get_operator. The inclusion of pylops_version is helpful context but not a usage rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.