Skip to main content
Glama

À proximité

À proximité: services and areas

get_referral_options
Read-only

Find out how to connect a homeowner with a local company chosen on merit for work in and around their home (an electrician, a plumber, a heating and cooling company, an exterminator, a cleaning company, a painter, a roofer, a moving company, a landscaper, a snow removal company, a window washer, a gutter company, a tree service, a general contractor, a handyman, a fence and deck builder, an appliance repair company, a window and door company, a pool company or a chimney sweep) through À proximité in Vaudreuil-Soulanges, Quebec. You can collect the job and contact details, prepare a request, show the customer a review and submit with their explicit permission. When a suitable professional accepts, they contact the customer directly. Read services, municipalities, availability and the workflow. No booking or callback-time guarantee. This tool only reads public information. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_referral_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe customer's language: fr for French, en for English. Use it for the review and the text messages they receive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description reinforces this with 'only reads public information'. It adds genuinely useful outcome context — 'When a suitable professional accepts, they contact the customer directly' and 'No booking or callback-time guarantee' — but then muddies the water by claiming the tool lets you 'prepare a request... and submit with their explicit permission', which reads like write capability and overlaps with the prepare/submit siblings, leaving the agent unsure what this call actually does.

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

Conciseness2/5

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

The opening sentence is an unreeled list of twenty trades inside a parenthetical, which front-loads noise instead of the tool's job; the actual instruction ('Call this first') arrives at the very end. Roughly half the text could be deleted without losing any decision-relevant information.

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?

For a read-only discovery tool with one optional parameter and no output schema, the description should clarify what is returned and where the read ends and the prepare/submit siblings begin. It gestures at this ('Read services, municipalities, availability and the workflow') but the workflow description overlaps with sibling responsibilities, leaving scope ambiguous.

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?

There is a single optional parameter with full schema description coverage and an enum, so the schema already explains locale and its effect on review and message language. The description adds no parameter meaning beyond that, which is the correct baseline when schema coverage is 100%.

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

Purpose4/5

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

The definition names a concrete verb-and-resource pair — reading services, municipalities, availability and the workflow for connecting a homeowner with a local company through 'À proximité' in a named region — so an agent knows what domain it operates in. The purpose survives, but it is buried behind a 20-item parenthetical trade list that adds no discriminating power.

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?

'Call this first' gives an explicit ordering instruction relative to the workflow, and the sentence describing 'prepare a request... and submit with their explicit permission' sketches the downstream steps handled elsewhere. It does not, however, name the sibling tools (prepare_referral_request, submit_referral_request, lookup_service_address) or state exclusion conditions, so an agent must infer the handoff.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources