Skip to main content
Glama

Abstraxn

by com.abstraxn.mcp

Places / solar / aerial-view lookups (pay-per-call)

places.lookup
Read-onlyIdempotent

Places, solar, and aerial-view lookups, paid per call directly from the caller's own wallet via the x402 protocol — no Abstraxn account needed. Pick one action:

  • text_search_full ($0.08): full-detail place text search. Requires textQuery. Optional maxResultCount (1-5, default 5), excludeFields (default ["photos"]), pageToken, locationBias ({circle:{center:{latitude,longitude},radius}}), includedType, languageCode (default "en"), openNow, minRating (0-5), priceLevels.

  • text_search_partial ($0.02): same as text_search_full but returns fewer fields per place — cheaper for quick lookups. Same parameters.

  • nearby_search_full ($0.08): full-detail search for places within a radius. Requires locationRestriction ({circle:{center:{latitude,longitude},radius (0-50000)}}) — do NOT send a bare top-level latitude/longitude/radius. Optional includedTypes/excludedTypes (max 50 each), maxResultCount (1-5, default 5), excludeFields (default ["photos"]), languageCode (default "en"), rankPreference (POPULARITY default, or DISTANCE).

  • nearby_search_partial ($0.02): same as nearby_search_full, fewer fields, cheaper. Same parameters.

  • place_details_full ($0.05): full details for one place. Requires placeId — the exact place id returned by an earlier text_search/nearby_search result; do not invent or guess it. Optional excludeFields (default ["photos"]), languageCode (default "en").

  • place_details_partial ($0.02): same as place_details_full, fewer fields, cheaper. Same parameters.

  • solar_building_insights ($0.02): rooftop solar potential for one location. Requires latitude (-90..90) and longitude (-180..180). Optional requiredQuality (LOW/MEDIUM/HIGH, default HIGH).

  • solar_data_layers ($0.08): raw solar data layers for an area. Requires latitude, longitude. Optional radiusMeters (0.1-175, default 50), view (default "FULL_LAYERS"), requiredQuality (default HIGH), pixelSizeMeters (default 0.25, documented as one of 0.1/0.25/0.5/1.0 but not schema-enforced), exactQualityRequired (default false).

  • solar_rgb_image ($0.05): renders one of the solar_data_layers assets as a viewable image. Either id (the exact asset id already returned by an earlier solar_data_layers call — "Mode A"; do not invent or guess it) OR both latitude and longitude ("Mode B") is required — provide exactly one mode, not both. Optional radiusMeters (0.1-100, default 30, Mode B only), layer (default "rgb"), month (1-12), hour (0-23), format (png/jpeg, default png), scale (1-2, default 1), crop (default false), quality (1-100, default 85).

  • aerial_view_lookup_video ($0.01): check whether a rendered aerial-view video already exists / poll its render status. Exactly one of address or videoId is required — videoId must be the exact value returned by an earlier aerial_view_render_video call; do not invent or guess it.

  • aerial_view_render_video ($0.01): kick off rendering a new aerial-view video for an address. Requires address. Poll aerial_view_lookup_video with the returned videoId until ready.

Pagination: text_search_full/partial and nearby_search_full/partial return nextPageToken when more results exist — repeat the ORIGINAL call (same textQuery / locationRestriction / etc.) with pageToken set to page further. pageToken must be the exact nextPageToken value from that earlier response — do not invent or guess it. excludeFields: colon-separated nested-path syntax trims nested response fields, e.g. "organization:technologies" excludes just that sub-field. All place-search/details actions default-exclude photos if excludeFields is omitted — pass excludeFields: [] to include photos.

Prices above are indicative — the exact charge for a given call is always whatever the live payment challenge specifies for that request. The first call (no paymentPayload) returns paymentRequired; retry with the same arguments plus paymentPayload to complete payment and get the real result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNosolar_rgb_image (Mode A): asset id from a prior solar_data_layers call.
cropNosolar_rgb_image: crop to a circle, default false. Optional.
hourNosolar_rgb_image: hour for hourlyShade layer. Optional.
viewNosolar_data_layers: which layer set to return, default FULL_LAYERS. Optional.
layerNosolar_rgb_image: which layer to render, default "rgb". Optional.
monthNosolar_rgb_image: month for monthlyFlux/hourlyShade layers. Optional.
scaleNosolar_rgb_image: image scale factor, default 1. Optional.
actionYesWhich places/solar/aerial-view operation to perform.
formatNosolar_rgb_image: output image format, default png. Optional.
addressNoaerial_view_render_video: REQUIRED address to render. aerial_view_lookup_video: exactly one of address/videoId is required.
openNowNotext_search_full / text_search_partial: only return places currently open. Optional.
placeIdNoplace_details_full / place_details_partial: REQUIRED place id.
qualityNosolar_rgb_image: JPEG quality (1-100), default 85. Optional.
videoIdNoaerial_view_lookup_video: exactly one of address/videoId is required.
latitudeNosolar_building_insights / solar_data_layers / solar_rgb_image (Mode B): latitude.
longitudeNosolar_building_insights / solar_data_layers / solar_rgb_image (Mode B): longitude.
minRatingNotext_search_full / text_search_partial: minimum average rating filter (0-5). Optional.
pageTokenNotext/nearby search: pagination token from a previous nextPageToken. Optional.
textQueryNotext_search_full / text_search_partial: free-text query, e.g. "coffee shops in Brooklyn".
priceLevelsNotext_search_full / text_search_partial: filter by one or more price levels. Optional.
includedTypeNotext_search_full / text_search_partial: restrict to one place type, e.g. "restaurant". Optional.
languageCodeNotext/nearby search, place details: response language, default "en". Optional.
locationBiasNotext_search_full / text_search_partial: soft location bias. Optional.
radiusMetersNosolar_data_layers: radius in meters (0.1-175, default 50). solar_rgb_image (Mode B only): radius in meters (0.1-100, default 30). Optional.
excludeFieldsNoNested-path field names to exclude from the response (colon-separated for nested paths, e.g. "organization:technologies"). Defaults to ["photos"] on every place-search/details action if omitted — pass [] to include photos. Optional.
excludedTypesNonearby_search_full / nearby_search_partial: place types to exclude. Optional.
includedTypesNonearby_search_full / nearby_search_partial: place types to include. Optional.
maxResultCountNotext/nearby search: max results per page (1-5, default 5). Optional.
paymentPayloadNox402 payment payload from a previous `paymentRequired` challenge. Omit on the first call.
rankPreferenceNonearby_search_full / nearby_search_partial: result ranking, default POPULARITY. Optional.
pixelSizeMetersNosolar_data_layers: pixel resolution in meters, default 0.25. One of 0.1/0.25/0.5/1.0 by convention but not schema-enforced. Optional.
requiredQualityNosolar_building_insights / solar_data_layers: minimum imagery quality, default HIGH. Optional.
locationRestrictionNonearby_search_full / nearby_search_partial: REQUIRED hard boundary — {circle:{center:{latitude,longitude}, radius (0-50000)}}.
exactQualityRequiredNosolar_data_layers: fail instead of falling back to lower quality, default false. Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
paymentRequiredNo

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the bar is lower. The description adds significant behavioral context: the x402 payment flow (first call returns paymentRequired, retry with paymentPayload), pagination loops, default excludeFields behavior, and the two modes for solar_rgb_image (Mode A with id, Mode B with lat/lng). It does not contradict any annotation. Slightly less than 5 because the description is lengthy and some details (like defaults) are also in the schema.

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 well-structured with a bulleted list of actions, making it scannable. It front-loads the core concept (paid per call, pick one action). However, it is verbose, repeating 'same parameters' for partial variants and including many examples. Given the complexity (11 actions, 34 parameters, payment protocol), the length is justified. A score of 5 would require slightly more conciseness, such as summarizing partial variants more compactly.

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?

Given the high complexity (34 parameters, 11 actions, nested objects, payment protocol, output schema exists), the description is remarkably complete. It covers every action with required and optional parameters, defaults, special behaviors (modes, pagination, field exclusion syntax), and the two-step payment flow. It also notes that prices are indicative. The output schema is not shown, but the description does not need to explain return values. No gaps are apparent.

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

Parameters5/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 adds substantial value beyond the schema: it explains the payment flow for paymentPayload, the colon-separated nested syntax for excludeFields, the two operational modes for solar_rgb_image, and the constraint that locationRestriction must be a nested circle object (not bare lat/lng/radius). It also provides default values and usage patterns (e.g., 'pageToken must be the exact nextPageToken from that earlier response'). This enriches the parameter semantics significantly.

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 explicitly states the tool's purpose: 'Places, solar, and aerial-view lookups, paid per call directly from the caller's own wallet via the x402 protocol'. It enumerates 11 distinct actions, each with a brief description of what it does and how it differs from others (e.g., full vs partial, search vs details). This clearly distinguishes between sibling actions and states the core resource (places, solar, aerial views).

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

Usage Guidelines5/5

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

The description provides explicit guidance for each action: required parameters, optional parameters, defaults, and critical constraints (e.g., 'do NOT send a bare top-level latitude/longitude/radius' for nearby_search_full, 'do not invent or guess it' for placeId and videoId). It also explains the two-step payment protocol ('first call returns paymentRequired; retry with paymentPayload'), pagination mechanics, and when to use partial vs full actions (cheaper, fewer fields). No alternative tools are needed since siblings are unrelated.

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

All Abstraxn toolsInspect
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

A4.1/5.0
Disambiguation4/5

Tools are grouped by domain (market, network, places, social, travel, web3) and each has a distinct purpose. However, within the 'network' group, tools like token_price, token_info, and market.crypto/price_feed could be confused for similar price lookups, but descriptions clarify their differences (free vs paid, DEX vs CoinGecko).

Naming Consistency3/5

The naming uses a dot-separated domain prefix (e.g., market.crypto, network.blocknumber, places.lookup) which is consistent in structure, but the action selection within each tool (e.g., search vs price_feed) is not reflected in the tool name itself. This hybrid approach is clear but not strictly uniform.

Tool Count4/5

With 11 tools covering a wide range of domains (crypto, network, places, social, travel, web3), the count is appropriate for a multi-purpose server. Each domain has a focused set of actions, so the tool count feels well-scoped without being excessive.

Completeness3/5

The server covers a broad but shallow surface across multiple domains. For example, crypto market data is well-covered, but places lacks a reverse geocode or photo tool. Travel has only flight and hotel search, missing car rentals or activities. The network domain is relatively complete for read operations, but lacks write support beyond prepare_transfer.

Resources