opportunity-exchange

evaluate_pathways

The decision tool: evaluate realistic routes into work for a person's stated credentials, education, experience, driver licence, relocation boundary, housing and family needs, savings, and retraining limit. Returns pass/conflict/unknown plus the same ordered, versioned evidence panel used by REST and the human evaluator. OSINT and placeholder values are excluded from ranking. Request-scoped: constraints are evaluated in-process and never stored.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Ranked list size (default 8, max 20).
`credentials`	No	Credential names held and current, e.g. "WHMIS", "Class 5 Licence".
`licenceClass`	No	Highest Saskatchewan driver licence currently held.
`householdSize`	No	People represented by the regional Market Basket Measure basket.
`incomeEarners`	No	Income earners sharing housing and utilities.
`educationLevel`	No	Highest education level.
`savingsDollars`	No	Cash available for training before funding.
`experienceAreas`	No	Capability areas with real working experience.
`bedroomsRequired`	No	Rental unit size required by the household.
`vehicleAvailable`	No	Whether the scenario includes a vehicle commute.
`targetOccupationId`	No	Role id from list_roles — evaluates that target in depth.
`maximumRelocationKm`	No	Maximum move from currentMunicipalityId; zero means local only.
`housingBudgetMonthly`	No	Maximum monthly rent for the requested household.
`currentMunicipalityId`	No	Current community, required when maximumRelocationKm is supplied.
`allowedMunicipalityIds`	No	Optional destination allowlist.
`maximumRetrainingWeeks`	No	Maximum acceptable retraining time; zero means direct entry.

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description details the return format (pass/conflict/unknown and evidence panel), non-storage of request data, and exclusion of OSINT/placeholders. It lacks explicit assurances of read-only nature or authentication needs, but the information provided is clear.

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

Conciseness4/5

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

The description is three sentences, efficient and focused. The first sentence is long but lists all inputs. Some repetition of 'same...panel' could be condensed, but overall it's well-structured.

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

Completeness3/5

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

Given 16 parameters, no output schema, and no annotations, the description adequately summarizes inputs and outputs but does not explain ranking logic or evidence panel contents, leaving gaps in understanding.

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 baseline is 3. The description only summarizes parameter categories without adding new constraints or examples, providing no extra value beyond the schema.

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?

The description clearly states the tool evaluates realistic routes into work based on detailed personal and contextual inputs, and distinguishes from sibling tools like 'compare_roles' or 'list_roles' by focusing on pathway evaluation.

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

Usage Guidelines3/5

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

The description implies usage for evaluating pathways but does not explicitly compare to alternatives or state when not to use. Guidance like 'OSINT and placeholder values excluded' is helpful but not comprehensive.

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

All opportunity-exchange tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation1/5

Several tools are effectively duplicates or near-duplicates: get_emerging_signals is an explicit alias for list_economic_signals, resolve_entity and resolve_entities overlap heavily, and the markdown variants duplicate their non-markdown reports. Pairs like compare_communities/compare_municipalities and search_businesses/search_licensed_businesses also require reading long contracts to avoid misselection.

Naming Consistency4/5

Tool names overwhelmingly follow a snake_case verb_noun pattern with sensible verbs like get_, list_, search_, and compare_. The main deviations are the backwards-compatible get_emerging_signals alias and prefix choices such as check_business_health vs get_business_health that obscure the underlying distinction.

Tool Count1/5

70 tools is an extreme surface for any MCP server, far beyond the 25+ 'too many' threshold. The set is fragmented by format variants, aliases, and multiple overlapping lookup tools, making selection and maintenance costly.

Completeness3/5

The domain surface is broad: entity resolution, business health, labour, community economy, procurement, and governance evidence are all covered in depth. However, there are notable lifecycle gaps—no sandbox deletion, consent revocation, health-action cancellation, or actual exchange/connect/apply step—that leave agents with dead ends.

Resources

Need Help?