Locate tables in a PowerDesigner model by matching a substring in their name or code. Case-insensitive search returns paginated results for quick schema inspection.
Search tables by substring in code or name (case-insensitive).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| query | Yes | ||
| model_id | Yes | ||
| page_size | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavioral traits. It adds case-insensitivity and substring matching, but omits crucial details such as pagination behavior, return format, and whether the operation is read-only. This leaves significant behavioral gaps.
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, front-loaded sentence with no wasted words. It efficiently conveys the core operation and key constraint (case-insensitive substring) without redundancy.
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 tool with 4 parameters, 2 required, and no output schema, the description is incomplete. It does not explain required parameters or pagination semantics, so an agent cannot reliably construct a correct invocation. The essential context is missing.
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 description coverage is 0%, so the description must explain parameters. It implies 'query' is the substring but does not clarify the roles of 'model_id', 'page', or 'page_size'. This fails to compensate for the missing schema descriptions, leaving parameter semantics underdefined.
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?
Description clearly states the verb 'Search', the resource 'tables', and specifies the matching method (substring in code or name, case-insensitive). This differentiates it from list_tables and get_table, making the tool's purpose immediately unambiguous.
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 like list_tables or search_columns. The description implies usage for substring-based lookup but does not state exclusions or conditions, leaving the agent to infer appropriate contexts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.