workana-mcp

Overview Schema Source Related Servers Discussions Admin

workana_buscar_proyectos

Read-onlyIdempotent

Search open Workana projects with filters and get an opportunity score (0-100) based on stack fit, competition, budget, client, and freshness.

Instructions

Busca proyectos abiertos en Workana con filtros y les pone un puntaje rápido de oportunidad (0-100) según encaje con tu stack, competencia, presupuesto, cliente y frescura. Solo lee el listado público: para datos del cliente (proyectos pagados, antigüedad) usa workana_evaluar_proyecto.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`texto`	No	Texto libre, p. ej. 'dashboard', 'ecommerce', 'api'.
`idioma`	No	Idioma del proyecto.	es
`skills`	No	Skills de Workana (se combinan con O). Acepta nombres ('React', 'Node.js', 'TypeScript') o slugs ('react-js', 'node-js', 'typescript', 'next-js', 'express-js', 'nest-js', 'javascript', 'react-native', 'vue-js', 'angular', 'mongodb', 'mysql', 'sql', 'api', 'rest-api', 'firebase', 'docker', 'python', 'php', 'laravel', 'wordpress', 'shopify', 'chatbot', 'web-scraping'). Vacío = tu stack por defecto (React, Node, TypeScript, Next, Express, Nest). Pasa [] junto con 'texto' para buscar solo por texto.
`formato`	No	'markdown' para leer, 'json' para procesar.	markdown
`categoria`	No	Categoría de Workana.	programacion
`modalidad`	No	Tipo de contrato.
`mis_skills`	No	Tu stack para calcular el encaje. Vacío = perfil por defecto (React, Node, TypeScript, Next…).
`publicados`	No	Antigüedad máxima del proyecto.	semana
`ordenar_por`	No	Orden del resultado.	oportunidad
`pais_cliente`	No	Código ISO del país del cliente, p. ej. 'AR', 'MX', 'ES', 'US'.
`subcategoria`	No	Subcategoría (solo para 'programacion').
`max_consultas`	No	Máximo de peticiones al listado. Sin sesión Workana oculta 13 de cada 20 resultados, así que el servidor divide la búsqueda (por skill, modalidad, propuestas, subcategoría) para verlos todos. Más consultas = más completo pero más lento (~1,5 s c/u).
`max_propuestas`	No	Descarta proyectos con más propuestas que esto.
`tarifa_min_hora`	No	Descarta proyectos por hora cuya tarifa máxima sea menor (USD/h).
`pocas_propuestas`	No	Solo proyectos con 0-4 propuestas.
`presupuesto_min_usd`	No	Descarta proyectos de precio fijo cuyo máximo sea menor.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/openWorld and the safety profile, but the description adds the non-obvious behavior that results carry a computed opportunity score across five factors, and that it reads only the public listing. Rate-limit/scraping details live in the schema, not here, so it is not fully self-contained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences: the first front-loads purpose plus the scoring behavior, the second handles scope and the alternative. No filler, and the most decision-relevant content comes first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and the annotations plus the description cover the safety and scope profile. The only gap is that it does not point to the remaining sibling tools or note result volume limits, which the schema partially covers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 16 parameters with enums, defaults, and semantics (e.g. max_consultas explains the request-splitting behavior). The description adds no parameter-level detail beyond loosely naming the scoring factors, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Busca), resource (proyectos abiertos en Workana), and an added behavior (scoring 0-100 by fit/competition/budget/client/freshness). It explicitly names the sibling workana_evaluar_proyecto as the tool for client data, so an agent can distinguish it without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names a concrete alternative and the condition that routes to it ('para datos del cliente... usa workana_evaluar_proyecto') and scopes the tool with 'Solo lee el listado público'. It does not mention the other siblings (workana_mejores_oportunidades, workana_ver_proyecto), so guidance is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server