Skip to main content
Glama
chrischall

angi-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

angi_get_pro

Read-onlyIdempotent

Fetch an Angi pro profile by URL for business details, service area, hours, amenities, awards, tasks, address, ratings breakdown, and review count.

Instructions

Read one Angi pro's full profile: business details, service area, hours, amenities, awards, tasks offered, contact address, and the ratings breakdown. Also reports how many reviews the page carries (fetch them with angi_get_reviews).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
compactNoDeprecated: use `view` instead (compact: true = view "compact", false = view "full"). Ignored when `view` is set.
profileUrlYesThe pro's Angi profile URL or site-relative path, as returned in `profileUrl` by angi_search_pros (e.g. "/companylist/us/nc/charlotte/mkb-plumbing-and-septic-llc-reviews-8535260.htm").

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 instead of the full record."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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds value beyond them by disclosing the return surface (ratings breakdown, contact address, a review count that is not the reviews themselves) and by flagging that reviews must be retrieved separately — useful behavior for a tool with no output schema.

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, both earning their place: the first front-loads the resource and its contents, the second handles sibling routing and the review-count caveat. No redundancy or filler.

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?

For a single-record read with no output schema, the description compensates by enumerating the returned profile sections and noting the separate review-count/review-fetch distinction. Combined with annotations covering safety and a fully documented schema, an agent has everything needed to call it correctly.

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%, and the schema itself explains profileUrl's expected format, the view enum, and the deprecated compact flag. The description adds no parameter-level detail, so the baseline 3 applies; the schema carries the full burden and does so adequately.

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 (read) and resource (one Angi pro's full profile) and enumerates exactly what the profile contains: business details, service area, hours, amenities, awards, tasks offered, contact address, and ratings breakdown. The final sentence explicitly contrasts it with the sibling angi_get_reviews, so an agent can distinguish it from search/list tools without opening a 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?

The description tells the agent what to do when reviews are needed: 'fetch them with angi_get_reviews', routing the complementary task to the correct sibling. It does not state exclusions (e.g., when to prefer angi_search_pros), but the usage context for a single-record lookup is clear.

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