Skip to main content
Glama

Find Flathead Valley pros

find_pros
Read-only

List the businesses in the Flathead Trades directory for a kind of work, optionally in one town, with phone numbers, websites and a link to each listing. Covers Whitefish, Columbia Falls, Evergreen, Kalispell, Somers, Bigfork, Lakeside and Polson, Montana.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trade": "<trade>"
    },
    "name": "find_pros"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoOptional town in the Flathead Valley, e.g. "Kalispell" or "Whitefish".
tradeYesThe kind of work, e.g. "roofing", "plumber", "electrician", "builder", "septic", "tree removal".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds useful context by naming exactly what each result contains and enumerating the covered towns, bounding the data set to the Flathead Valley. It does not mention result limits, pagination, or empty-result behavior, keeping it short of a 5.

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 sentences, front-loaded with the core action and return contents, followed by the geographic scope. Every clause carries information an agent would need; nothing is padding.

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 no output schema, the description usefully enumerates the returned fields (phone, website, listing link) and the covered region, which is enough to call the tool correctly. Minor gaps remain around result volume and what happens when a trade/town combination yields nothing.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented, but the description adds meaning beyond the schema by clarifying that town is optional and enumerating the eight valid towns for that filter while framing trade as the required dimension. This meaningfully reduces ambiguity in the town parameter, though it adds nothing about trade syntax beyond the schema examples.

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?

States a specific verb and resource — listing businesses from the Flathead Trades directory filtered by a kind of work — and spells out the return fields (phone, website, listing link). It is clearly distinguishable from list_trades_and_towns and start_quote, though it never names them to make the contrast explicit.

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 purpose implies when to use it (look up contractors by trade, optionally narrowed to a town), but there is no explicit routing guidance such as 'call list_trades_and_towns first to discover valid trade/town values' or 'use start_quote to request a quote from one of these businesses'. Usage is inferable rather than stated.

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