wejob_search_formationsSearch public active WeJob formations.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Optional public result sort order. | |
| limit | No | Maximum number of results. | |
| query | No | Search query. | |
| skills | No | Comma-separated skills filter. | |
| company | No | Company filter. | |
| location | No | Location filter. |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / sortAdded value: +{
+ "description": "Optional public result sort order.",
+ "enum": [
+ "newest",
+ "oldest",
+ "deadline_soon",
+ "deadline_later",
+ "price_asc",
+ "price_desc",
+ "smallest",
+ "largest",
+ "founded_newest",
+ "founded_oldest",
+ "most_jobs"
+ ],
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds 'public active' constraint, but lacks additional behavioral details like pagination or filtering 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?
Single sentence with zero fluff, front-loaded with verb and resource.
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?
Despite high schema coverage and output schema, description lacks definition of 'formations' and proper usage context, leaving ambiguity for the agent.
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?
All 6 parameters have schema descriptions (100% coverage), so description adds no value beyond schema; baseline 3.
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 verb 'Search' and resource 'formations', differentiating from sibling tools like wejob_search_companies and wejob_search_jobs.
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 on when to use this tool versus alternatives; no exclusions or context provided.
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.