Search for tradespeople on meseriasi.ro by location and/or category (trade type). Returns a paginated list of matching profiles.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default 1) | |
| category | No | Trade type / profession category (e.g. "electrician", "instalator", "zugrav") | |
| location | No | City or region name to filter by (e.g. "București", "Cluj-Napoca") | |
| per_page | No | Results per page, max 50 (default 10) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It mentions pagination ('Returns a paginated list'), which is a behavioral trait, but lacks details on sorting, default behavior when no parameters are supplied, authentication requirements, or error cases. This is adequate but not comprehensive.
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 sentences long, front-loading the action and result. Every word is meaningful, with no redundancy or filler.
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 4 optional parameters, no output schema, and no annotations, the description covers the basic purpose and output. However, it omits details about result format, sorting, allowed combinations of parameters, and pagination semantics (e.g., how to navigate pages). Completeness is adequate but not thorough.
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 100%, with each parameter adequately described in the schema. The tool description adds no additional meaning beyond the schema ('by location and/or category' maps to 'location' and 'category' parameters). Baseline score of 3 applies.
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 the verb (Search for), resource (tradespeople), platform (meseriasi.ro), and search criteria (location and/or category). It also describes the output (paginated list of profiles). This distinguishes it from sibling tools like create_project or get_tradesperson_profile.
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?
The description implies usage for finding tradespeople but provides no explicit guidance on when to use this tool versus alternatives such as get_tradesperson_profile or start_conversation. No conditions or exclusions are mentioned.
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.
Each tool targets a distinct action: project creation, profile retrieval, OTP request, tradesperson search, and conversation initiation. No two tools have overlapping purposes, ensuring clear agent selection.
Tools generally follow verb_noun pattern (e.g., create_project, search_tradespeople). Minor inconsistency: 'tradesperson_profile' uses singular while 'tradespeople' uses plural, but overall pattern is consistent and readable.
With 5 tools covering project creation, search, profiles, and chat, the set is well-scoped for a homeowner-tradesperson matching server. Each tool serves a clear role without redundancy.
Core workflow is covered (create project, search, start conversation), but notable gaps exist: no tools for updating/deleting projects, viewing bids, or managing conversations. Agents may face dead ends.
