Skip to main content
Glama
chrischall

angi-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

angi_search_pros

Read-onlyIdempotent

Search Angi for home-service pros by trade and city. Get ratings, review counts, and profile details to compare contractors before hiring.

Instructions

Find home-service pros on Angi for a trade in a US city. Returns each pro with ratings (overall plus per-dimension: quality, value, punctuality, professionalism, responsiveness), review count, percent-recommended, years in business, service area and amenities. trade and city are Angi slugs — resolve them with angi_list_trades and angi_list_cities first. 10 pros per page; use page to walk further. Note Angi has no zip-code filter: location comes from the city slug only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity slug, e.g. "charlotte", "rock-hill".
pageNo1-based page number. 10 pros per page.
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns a slim projection of each record (falling back to the full record if the projection does not fit the payload); "full" returns Angi's whole records.
stateYesTwo-letter US state code, e.g. "nc".
tradeYesTrade slug, e.g. "plumbing", "roofing", "air-duct-cleaning".
compactNoDeprecated: use `view` instead (compact: true = view "compact", false = view "full"). Ignored when `view` is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.8
    • changedInput schema / properties / compact / description
      Previous value: -"Return a slim summary per pro instead of the full record. Recommended when browsing or ranking."New value: +"Deprecated: use `view` instead (compact: true = view \"compact\", false = view \"full\"). Ignored when `view` is set."
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns a slim projection of each record (falling back to the full record if the projection does not fit the payload); \"full\" returns Angi's whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description layers on genuinely non-obvious behavior: the exact fields returned (per-dimension rating breakdown, review count, percent-recommended, years in business, service area, amenities), page size, and the location limitation. That is real added context rather than restatement.

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?

Four sentences, front-loaded with purpose, then return shape, then prerequisites, then the pagination/location caveats. Dense and largely waste-free; the per-dimension rating enumeration is the only passage that runs slightly long against its value.

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

Completeness5/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 takes on the burden of describing returns and does so thoroughly, including the compact/full distinction's effect on payload shape. Prerequisites, pagination, and the missing-filter caveat round out everything an agent needs to invoke it correctly.

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 baseline is 3, but the description adds meaning the schema does not: `trade`/`city` must be Angi slugs resolved via sibling tools, and location derives only from the city slug. It says nothing about `page` semantics beyond page size or about the `view`/`compact` switch, which the schema carries alone.

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?

Opens with a specific verb+resource+scope: "Find home-service pros on Angi for a trade in a US city." An agent can immediately separate this from angi_get_pro (single pro) and the list_* helpers, which are named as prerequisites.

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?

Explicitly states the prerequisite (resolve `trade` and `city` via angi_list_trades / angi_list_cities first) and gives pagination guidance ("10 pros per page; use `page` to walk further"), plus the constraint that no zip-code filter exists. It never spells out when-not to use this versus angi_get_pro, so 4 rather than 5.

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

Deploy Server

Other Tools