Skip to content

MCP

MCP tools

MAIA's MCP connector exposes twenty-three tools. With them an MCP client can find a place or a county, start a project, bring in a file, send a request to MAIA's agent, query a project's data, share a project, follow the run, answer its questions, ask you to approve its steps, save skills and memory, and send feedback to the MAIA team.

This inventory follows the published connector release. The tools listed by your connected client are authoritative for your workspace. When search_docs is offered by your connector, ask your assistant to use it for questions about MAIA capabilities, the data MAIA has and where, setup, pricing, and integrations. It returns matching published documentation and data catalog entries with source links and workspace availability restrictions. Otherwise, use maia_guide and the MAIA docs.

Every tool at a glance#

find_countyWhat it doesFinds US counties by name, and whether you can build projects in them, plus cities and towns of that nameChanges dataNo
find_placesWhat it doesFinds the counties of US cities, neighborhoods, ZIP codes, metros, and regions, and whether you can build projects in themChanges dataNo
create_projectWhat it doesCreates a project in one county or several, in named places, or in an area you draw, and starts MAIA on a request or a skillChanges dataYes
import_rowsWhat it doesImports rows passed as CSV or GeoJSON text into a project, or into a new project in a countyChanges dataYes
get_upload_linkWhat it doesGets a one-use link to bring a file into a project, or into a new project in a countyChanges dataYes
get_importWhat it doesReports an address import: rows matched, rows not matched and why, or why it failedChanges dataNo
send_messageWhat it doesSends another request, or runs a skill, on an existing projectChanges dataYes
get_runWhat it doesReports a run: progress, then the answer, a question, work stopped at the time limit, or an errorChanges dataNo
respondWhat it doesAnswers MAIA's question, or declines its approvalChanges dataYes
approve_stepWhat it doesApproves the step MAIA is waiting on, after you say yesChanges dataYes
stop_runWhat it doesStops the current run. Work saved before the stop stays in the projectChanges dataYes
list_projectsWhat it doesLists the projects you can see, most recently updated firstChanges dataNo
get_projectWhat it doesDescribes a project: layers, columns, row counts, and viewsChanges dataNo
project_schemaWhat it doesLists the tables and columns query_project can read in a projectChanges dataNo
query_projectWhat it doesRuns one read-only SQL query over a project's layers and returns its rows. A query over parcel data spends your workspace's parcel export budgetChanges dataYes
set_project_sharingWhat it doesSets which teammates can open a project you own, or turns its public link offChanges dataYes
share_project_publiclyWhat it doesTurns on a public link to a project you own, after you say yesChanges dataYes
maia_guideWhat it doesReturns what MAIA does, requests that work well, and its limitsChanges dataNo
search_docsWhat it doesSearches MAIA's published docs and data catalog for capabilities, the data MAIA has and where, setup, pricing, and integrationsChanges dataNo
list_skillsWhat it doesLists your skills and your workspace's skillsChanges dataNo
save_skillWhat it doesSaves one of your own skillsChanges dataYes
save_to_maia_memoryWhat it doesSaves a titled note to your MAIA memoryChanges dataYes
send_feedbackWhat it doesSends the MAIA team a short report: a wrong result, an error, something MAIA can't do, a feature request, a confusing reply, a slow run, or praiseChanges dataYes

Three more tools exist only for the in-chat project view. Your client does not call them.

maia_guide#

No parameters. Returns a short guide written for your client to read before it uses MAIA.

search_docs#

queryTypestring, up to 500 charactersRequiredYesMeaningA product question or feature/setup keywords

Returns up to five matching sections from MAIA's published docs and from the data catalog in MAIA's web app, with page titles, section headings, source links, and your workspace's availability restrictions. Each dataset in the catalog is one section, with its coverage and a link to its catalog page. Use it for questions about capabilities, the data MAIA has and where, setup, pricing, and integrations. Cite the source links and respect the availability restrictions. A feature described in the docs may still need MAIA staff to enable it for your workspace.

If no section matches, try a feature name or a more specific question. No match does not mean MAIA cannot do it. If the docs cannot be fetched and no unexpired cached copy is available, the tool returns an error. It never returns the whole documentation set.

Starting work#

find_county#

queryTypestringRequiredYesMeaningCounty, city, or town name, optionally with state, such as "Maricopa, AZ" or "Boulder, CO"

Returns each matching US county with its county_fips and name. A county your workspace cannot use is flagged unavailable, and create_project says why. A county outside your plan that your workspace can still add as its free county of choice is flagged can_be_county_of_choice instead. create_project adds it when you ask for a project in it. Your client should never pick one you did not name. When nothing matches and your workspace can use 20 counties or fewer, it also returns all of them as available, so your client can offer you one. When no county or place matches, it says that MAIA covers the United States today and that places in other countries are coming soon, and suggests trying a county or city name with its state, or a 5-digit county code. An empty query is refused.

It also returns up to five cities and towns of that name as places, each with its place_id, name, and the county codes it lies in, main county first. Pass a place_id to create_project as place for a project that covers that city or town instead of its whole counties.

{ "county_fips": "04013", "name": "Maricopa County, AZ" }

Pass county_fips on as a string. As a number it loses its leading zero.

find_places#

queryType{"anyOf":[{"maxLength":200,"minLength":1,"type":"string"},{"items":{"maxLength":200,"minLength":1,"type":"string"},"maxItems":200,"minItems":1,"type":"array"}]}RequiredYesMeaningA city, neighborhood, ZIP code, metro, or region. For several places, a list with one place per item, with its state where known

Looks places up with the same place search as MAIA's web app, and creates nothing. It does not search for businesses. Returns the counties the places lie in that your plan covers as counties, and the others as unavailable_counties, each with its county_fips, name, and state. Names that matched nothing come back as unmatched_places, and next_step then says that MAIA covers the United States today and that places in other countries are coming soon. county_limit and outline_limit give the most counties and city or neighborhood outlines one project can hold, and within_county_limit and within_outline_limit say whether these places fit. next_step says what to do next.

When a name could mean more than one place, it returns ambiguous: the name, and each place it could be with its state, population, and counties. The lookup stops at that name. Your client asks you which you mean, then looks up your choice as labeled. When two places share a label, the label adds the county. An empty query is refused.

To build over these places, your client passes the same names to create_project as places, so cities and neighborhoods keep their outlines. To cover their whole counties instead, it passes the county codes as county_fips and additional_counties. To learn whether an unavailable county can be your county of choice, use find_county.

create_project#

county_fipsTypestring, 5 digitsRequiredUnless places or area is setMeaningThe county code from find_county or find_places
requestTypestringRequiredUnless skill is setMeaningWhat to build, in plain language
skillTypestringRequiredNoMeaningThe name of a skill from list_skills for MAIA to run
request_idTypestring, up to 128 charactersRequiredNoMeaningAn id your client chooses before the call. A retry with the same id and the same parameters returns the original project, run, and notices instead of starting again
additional_countiesTypelist of string, up to 199 itemsRequiredNoMeaningMore county codes from find_county, for one project over several counties. The project keeps them in the order given
placeTypestring, 7 digitsRequiredNoMeaningA place_id from find_county. The project covers that city or town in county_fips and in any additional_counties it lies in, instead of those whole counties. Other additional_counties are kept whole
workspace_accessTypeprivate, workspace_read, or workspace_writeRequiredNoMeaningWhich teammates in your MAIA workspace can open the project: none, all of them to view, or your workspace's writers to edit and the others to view. Your client asks you whether teammates may edit when you have not said
placesTypelist of string, 1 to 200 items, each up to 200 charactersRequiredNoMeaningCities, neighborhoods, ZIP codes, metros, or regions, one per item with its state where known, as given to find_places. The project covers them instead of whole counties. Given alone, without county_fips, additional_counties, place, or area
areaTypeGeoJSON objectRequiredNoMeaningA drawn outline for the project: a Polygon or MultiPolygon with [longitude, latitude] coordinates in WGS84. Not with places or place

For a project over several counties, pass the first county as county_fips and the others as additional_counties. Give each county once. A place is refused unless it came from find_county with county_fips among its counties. additional_counties and place need county_fips, and a call with none of county_fips, places, and area is refused.

With places, every name must resolve before MAIA makes the project: a name that matches nothing or could mean more than one place, places over the county or outline limit, or a county your plan cannot take is refused, with the reason, and makes no project. Cities and neighborhoods keep their outlines. When MAIA cannot find a place's outline, the project covers its whole counties and notice says so. ZIP codes, metros, and regions cover their whole counties.

With area, the project takes each county that overlaps at least 1% of the area or 1% of the county, largest overlap first. With county codes as well, the project keeps those counties, and each must meet the same overlap rule. An area that touches no county, has coordinates out of range, has a ring that is not closed or has fewer than 4 positions, or is too complex is refused before any project is made. Each ring's last position must repeat its first. When an area touches no county, the refusal reminds your client that positions are [longitude, latitude], and says that MAIA covers the United States today and that places in other countries are coming soon.

The project starts private unless workspace_access says otherwise. Workspace access is refused when your workspace has no other members. A public link is separate, and never set at creation: turn one on later with set_project_sharing and share_project_publicly. A retry with the same request_id and different parameters, such as a different workspace_access, is refused, and starts no new work.

Returns at once with a run report holding the project id and the run id. Follow the run with get_run. The report's fields are on Runs and approvals. When there is something to tell you about the new project, such as that its counties are large enough to make queries slower, the report carries it as notice.

When your plan cannot take a county, or MAIA has no data for it, create_project makes no project. Its result says why, and what you can do, as not_created in place of a project.

A free self-serve workspace can add one county outside its plan, once and for good, as its county of choice. After that, only a plan upgrade opens more counties. When you ask for a project in a county flagged can_be_county_of_choice, and you are a workspace admin, create_project adds the county to your workspace and creates the project in the same call. The result's county_of_choice_added says so. The choice cannot be changed later.

send_message#

project_idTypestringRequiredYesMeaningThe project to work on
messageTypestringRequiredUnless skill is setMeaningThe next request
skillTypestringRequiredNoMeaningThe name of a skill to run on this project
request_idTypestring, up to 128 charactersRequiredNoMeaningAn id your client chooses before the call. After an error or a lost response, a retry with the same id and the same parameters returns the original outcome, run, and notices instead of doing the work again. Use a new id for new work

Returns at once with a run report. Use it for questions about the data too. MAIA refuses a new request while a run is in progress on the project, so wait until get_run no longer reports running. A new request cancels a question or approval MAIA is waiting on: the earlier run's status becomes cancelled, and its pending step is not done. So when none of a question's options fits, a new request answers it in your own words. To pick an option or decide an approval, use respond or approve_step instead.

To add counties to the project, name them in message. The run's answer names the counties added, or why they were refused. Adding counties widens the project's area. It does not refill the project's existing layers.

Bringing in a file#

The steps, from your side, are on Upload a file. Your client passes a CSV or GeoJSON file to import_rows, and sends a larger file, or another format, to a link from get_upload_link.

import_rows#

contentTypestring, up to 100,000 charactersRequiredYesMeaningThe rows as CSV text with a header row, or as GeoJSON text
file_formatTypecsv or geojsonRequiredNoMeaningThe format of content. Defaults to csv
project_idTypestringRequiredUnless county_fips is setMeaningA project you can edit, to add the rows to
county_fipsTypestring, 5 digitsRequiredUnless project_id is setMeaningThe county code from find_county. The import creates a new project there
layer_nameTypestring, up to 40 charactersRequiredNoMeaningThe new layer's name, shown as its label in the layer list. Address matching can reuse a layer for the same properties instead. A new project built from addresses names its layer itself
truncateTypebooleanRequiredNoMeaningtrue imports only the first rows when there are more than the row limit. Defaults to false. Your client asks you first
match_addressesTypebooleanRequiredYesMeaningtrue matches property addresses to parcels or places. false makes rows with coordinates or shapes a map layer, and any other rows a table
address_mappingTypeobjectRequiredNoMeaningThe columns that hold the property address, by their exact names: street, the street or full address, and optionally house_number, unit, city, state, and zip. Leave it out to let MAIA pick them, and when match_addresses is false

Your client chooses whether to match addresses. When it does not pass address_mapping, MAIA picks the address columns. When the columns leave it unsure, no import starts: your client asks you which column holds the street or full address, and which hold the unit, city, state, and ZIP, then sends your answer as address_mapping. Other columns stay in the layer as data. A column name in address_mapping that is not in the rows is refused, with the names that are. Address matching needs a project with a county.

Returns the same response as an upload to a link: the project and, for address matching, an import_id to follow with get_import. The rows go through the same import as a file upload.

project_idTypestringRequiredUnless county_fips is setMeaningA project you can edit, to add the file to
county_fipsTypestring, 5 digitsRequiredUnless project_id is setMeaningThe county code from find_county. The upload creates a new project there
layer_nameTypestring, up to 40 charactersRequiredNoMeaningThe new layer's name, shown as its label in the layer list. Defaults to the file name. Address matching can reuse a layer for the same properties instead. A new project built from addresses names its layer itself
truncateTypebooleanRequiredNoMeaningtrue imports only the first rows of a file over the row limit. Defaults to false. Your client asks you first
match_addressesTypebooleanRequiredYesMeaningtrue matches property addresses to parcels or places. false makes a file with coordinates or shapes a map layer, and any other file a table
address_mappingTypeobjectRequiredNoMeaningThe columns of the file that hold the property address, by their exact names: street, the street or full address, and optionally house_number, unit, city, state, and zip. Leave it out to let MAIA pick them, and when match_addresses is false

Returns a one-use link and the command that sends the file to it. The link expires after 10 minutes and works only for you. Your client sends the file from its own code environment, not through a tool call. The response to the upload names the project and, for address matching, an import_id to follow with get_import. MAIA picks the address columns as it does for import_rows, and when it is unsure, the upload starts no import and your client asks you which columns hold the address. The upload refuses a column name in address_mapping that is not in the file, and address matching in a project without a county. When the column names make the link too long, use shorter ones.

get_import#

import_idTypestringRequiredYesMeaningThe import_id from the upload's response
wait_secondsTypeinteger, 0 to 30RequiredNoMeaningHow long to wait for the import to finish before answering. Defaults to 30

Returns the import's progress, then the rows matched to parcels and the rows not matched, with the reason for each. If the import failed, it says why. A failed import that gives no failure reason added no rows, and the reasons rows were not matched explain why. When some rows lie in counties outside the project, county_note names those counties and says whether your workspace can open them, and the upload's response gives the same note. Those rows are not matched. To match them in a county your workspace can open, your client asks you first, then asks MAIA with send_message to add the county, and imports the file again. A file sent to a link needs a new link from get_upload_link. Only an address import needs it: a map layer or a table is in the project when the upload returns. When the import finishes, get_project shows the layers it made or added to.

Following a run#

When your client supports MCP tasks, create_project, send_message, respond, approve_step, and an address import with import_rows can return a task instead of a run report or an upload response. Your client then follows the task itself, and does not need get_run or get_import. A run that is still going is working, with its current step. A run that ends, or fails, is completed with the report get_run gives. A run that was stopped, or whose step a newer request set aside, is cancelled. An import task is completed with the report get_import gives. A result with something to tell you, such as a notice, a step set aside, or an import cut to the row limit, comes back as an ordinary result instead. Cancelling a task stops its run, or cancels its import.

When your client can also show a form, an approval MAIA is waiting on comes to you as a form to accept or decline, and the task follows the run that continues after your answer. Its final result starts with what MAIA said before it asked. Without forms, the approval comes back as a get_run report, and your client answers it with approve_step or respond. A question always comes back as a report for your client to answer with respond. Clients without tasks see no change.

get_run#

project_idTypestringRequiredYesMeaningThe project the run belongs to
run_idTypestringRequiredNoMeaningThe run id from create_project, send_message, or respond. Omitted, the project's current or latest run
wait_secondsTypeinteger, 0 to 30RequiredNoMeaningHow long to wait for the run to finish before answering. Defaults to 30. Keep it under your client's own tool timeout

Returns a run report. Its fields are described in Runs and approvals. A run whose pending question or approval a newer request set aside reports cancelled.

A run stops at 60 minutes. A run that reaches the limit reports incomplete, with what MAIA wrote so far. It may have saved some of its work: check the project, then ask MAIA to continue with send_message. The report's changed_layers lists the layers the run is confirmed to have created, changed, or deleted. The list may leave out saved changes, so an empty list does not prove nothing changed. Check the project before you ask for the same edits again.

After stop_run, pass the run_id it returned. running means the run has not finished stopping yet. A final stopped confirms it stopped.

respond#

project_idTypestringRequiredYesMeaningThe project that is waiting
choiceTypestringRequiredFor a questionMeaningThe id or the label of the option to pick
declineTypebooleanRequiredTo decline an approvalMeaningtrue declines the step. Defaults to false
noteTypestring, up to 2,000 charactersRequiredNoMeaningWhy you declined. MAIA reads it with the decline
request_idTypestring, up to 128 charactersRequiredNoMeaningAn id your client chooses before the call. After an error or a lost response, a retry with the same id and the same parameters returns the original outcome, run, and notices instead of doing the work again. Use a new id for new work

Send choice for a question and decline for an approval. The report says which kind is pending. A call with the wrong one, or with nothing pending, is refused. A choice that matches an option's id picks that option. A label that more than one option shares is refused, with each of those options' ids. A choice that is not an option is refused, with the options listed as id and label. respond takes no answer in your own words: when no option fits, send the answer with send_message. respond never approves a step. To approve, use approve_step.

{ "project_id": "3f6c1a2e-0000-0000-0000-000000000000", "choice": "a" }
{ "project_id": "3f6c1a2e-0000-0000-0000-000000000000", "decline": true, "note": "Too many rows. Offer a smaller run." }

Returns the run report. The run continues.

approve_step#

project_idTypestringRequiredYesMeaningThe project that is waiting
approval_idTypestringRequiredYesMeaningThe approval_id of the pending approval from get_run
summaryTypestringRequiredYesMeaningThe summary of the pending approval from get_run, unchanged
noteTypestring, up to 2,000 charactersRequiredNoMeaningA note MAIA reads with the approval
request_idTypestring, up to 128 charactersRequiredNoMeaningAn id your client chooses before the call. After an error or a lost response, a retry with the same id and the same parameters returns the original outcome, run, and notices instead of doing the work again. Use a new id for new work

Lets MAIA run the step it asked approval for. approval_id and summary must match the pending approval exactly. A call that does not match, or with no approval pending, is refused.

{
  "project_id": "3f6c1a2e-0000-0000-0000-000000000000",
  "approval_id": "toolu_01A2B3C4D5E6F7G8",
  "summary": "Enrich 1,200 rows of Owner contacts on Parcels. That is past your 500-row limit per reply. This run uses 1,200 credits, and leaves 3,800."
}

Returns the run report. The run continues.

Note

approve_step is marked destructive, so your client asks you before each call. The request shows the summary, so you see what the step does and what it uses. If you set the tool to "always allow" in your client, it no longer asks.

stop_run#

project_idTypestringRequiredYesMeaningThe project whose run to stop

Requests a stop. It returns whether a run was in progress and, if so, its run_id, but not that the run has stopped. A stop is not instant. MAIA halts at the next safe point. Check the project for the work it saved before the stop. Follow the run_id with get_run until the run is no longer running, and go by its final status: the run may finish before the stop takes effect. Calling it twice is safe.

Reading projects#

list_projects#

limitTypeinteger, 1 to 100RequiredNoMeaningHow many to return. Defaults to 25

Each project comes with its id, name, status, last update, and a link to it in MAIA.

get_project#

project_idTypestringRequiredYesMeaningThe project to describe

Returns the project's current counties, in project order, and its layers, each with its kind, row count, and column names. It also returns the views, and whether a run is in progress. For a project you own, it returns its sharing too, in the same form set_project_sharing returns. It does not return rows. To read them, use project_schema and query_project, or open the project link.

project_schema#

project_idTypestringRequiredYesMeaningThe project to read

Returns the relations and columns that query_project can read, with a handbook on how to query them. Your client calls it once before its first query. It does not list licensed property data: see query_project. A column marked own data holds MAIA's own records, names the counties it has values in, and can say what it holds. A parcel layer with MAIA's own sale records also has a __sales relation: one row for each recorded sale of the layer's parcels.

query_project#

project_idTypestringRequiredYesMeaningThe project to read
sqlTypestring, up to 10,000 charactersRequiredYesMeaningOne read-only SELECT over the relations from project_schema

The query changes no data in the project. A query over a layer that may hold parcel data spends your workspace's parcel export budget, so query_project is marked as changing data. Returns at most 1,000 rows and 512 KiB, whatever LIMIT the query sets. total_rows is how many rows the query returned, and truncated says whether a cap cut the result, so aggregate in SQL instead of paging rows out. Shared county tables are not available here. MAIA's own county records reach the query only as the own data columns and __sales relations that project_schema lists.

MAIA licenses some property data from partners for use inside MAIA. project_schema and query_project never return it: owner names, mailing and site addresses, parcel numbers, use codes, lot size, values, taxes, sale and building details, or a column copied from them. In some counties, MAIA serves its own records for some of these columns, listed as own data. Those are not the licensed values. An own data value is empty outside the counties it lists, for a parcel MAIA has no record for, and before MAIA has loaded its records. An empty value there does not mean the record is empty. A water or sewer status that no source fills reads unknown instead of empty. To work with the licensed values, ask MAIA's agent with send_message, which filters and researches inside MAIA, or sign in to MAIA to see them in the project.

When the connector's contact details setting is turned off for your workspace, project_schema and query_project also withhold phone numbers and emails from licensed property records in contact enrichments, along with any phone number or email in those enrichments' reasoning and sources, and the handbook says so. Contact details MAIA found through other research still appear. To see the withheld ones, open the project in MAIA.

Sharing a project#

A project starts private. Only its owner can change its sharing through the connector, even where MAIA lets a workspace writer manage the public link. An example project's sharing cannot be changed.

set_project_sharing#

project_idTypestringRequiredYesMeaningThe project to share, from create_project or list_projects
workspace_accessTypeprivate, workspace_read, or workspace_writeRequiredUnless public_link is setMeaningWhich teammates in your MAIA workspace can open the project: none, all of them to view, or your workspace's writers to edit and the others to view. Your client asks you whether teammates may edit when you have not said
public_linkTypebooleanRequiredUnless workspace_access is setMeaningfalse turns the public link off, and its URL stops working for good. true keeps an existing link

Returns the project's sharing: its workspace_access, and its public_link with the url, the access, and when it expires, or null when there is none. Workspace access is refused when your workspace has no other members, so invite teammates in MAIA first.

set_project_sharing never turns a public link on. With public_link set to true and no link yet, it changes nothing and returns a summary of what the link would open, for share_project_publicly.

Note

set_project_sharing is marked destructive, so your client asks you before each call.

share_project_publicly#

project_idTypestringRequiredYesMeaningThe project to share, from create_project or list_projects
summaryTypestringRequiredYesMeaningThe summary set_project_sharing gave for the link, unchanged

Turns on a public link that anyone can open, inside or outside your organization. Your client shows you the summary and calls this tool only after you say yes. summary must match exactly. When it no longer describes what the link would do, for example because the project's layers changed, nothing is changed and the refusal gives the new summary.

The link opens the project's map, layers, and chat. The project's layers decide which kind it is:

  • gated: viewers give a work email and accept MAIA's terms to see parcel details. The link expires in 14 days.
  • geometry_only: viewers do not sign in, and parcel details stay hidden. The link works until it is turned off.

Returns the project's sharing, with the link's url to give the people who should see it. If the project already has a link, it returns that one. To turn a link off, use set_project_sharing with public_link set to false.

Note

share_project_publicly is marked destructive, so your client asks you before each call. The request shows the summary, so you see who can open the project and what they see.

Skills and memory#

list_skills#

nameTypestringRequiredNoMeaningA skill's name, to get its full instructions

Without name, each skill comes back with its name, description, scope, and kind. The full instructions come back only for a skill asked for by name.

save_skill#

nameTypestring, up to 120 charactersRequiredYesMeaningThe skill's name. Saving the same name replaces your skill
descriptionTypestring, up to 400 charactersRequiredYesMeaningWhat the skill does and when MAIA should use it
instructionsTypestring, up to 32,000 charactersRequiredYesMeaningThe method itself
kindTypeworkflow, enrichment, or agent_columnRequiredNoMeaningA new skill defaults to workflow. An existing skill keeps its kind

Saves a personal skill. Workspace skills are edited in MAIA. See Skills.

save_to_maia_memory#

titleTypestring, up to 120 charactersRequiredYesMeaningA short section name. Saving the same title replaces that section
contentTypestring, up to 8,000 charactersRequiredYesMeaningThe note

MAIA reads this memory in every project. It is part of your personal knowledge. See Knowledge.

Note

Both save tools tell your client to show you the draft and get your yes first. Read the draft before you agree.

Feedback#

send_feedback#

kindTypewrong_result, error, missing_capability, feature_request, confusing, slow, praise, or otherRequiredYesMeaningWhat the report is about: a wrong or unusable answer, row, or value; a tool that failed; something the task needed that MAIA can't do; something you want MAIA to do or do better; an unclear reply or description; a run or answer that took too long; something that worked well; or anything else
messageTypestring, up to 2,000 charactersRequiredYesMeaningWhat was expected, what happened, and any workaround. It refers to data by project and run instead of copying it
user_askedTypebooleanRequiredYesMeaningtrue when you asked to send the report, false when your client raised it itself
impactTypeblocked, worked_around, or minorRequiredNoMeaningThe task could not be finished, it was finished another way, or the problem was small friction
toolTypestring, up to 64 charactersRequiredNoMeaningThe MAIA tool the report is about, such as get_run
project_idTypestring, up to 64 charactersRequiredNoMeaningThe project the report is about
run_idTypestring, up to 200 charactersRequiredNoMeaningThe run the report is about. It is linked only together with its project_id

Returns a note that the report was sent. Your client uses it when you ask, when you want something MAIA does not do, or when a MAIA tool failed or gave a wrong result, once per problem. It does not use it for a refusal caused by a mistake in its own arguments. When your client sends a report on its own, it tells you what it sent.

The report is stored and posted to MAIA's internal feedback channel with your email, your workspace, and your client's name. The team reviews reports but does not reply in the chat. Your client is told to leave out personal information, owner or contact details, and the rest of the conversation. A project is linked only when you can view it, and a run only when it belongs to that project. A reference that does not check out is dropped with a note, and the report is still sent. A tool name that is not one of MAIA's tools is kept as written, with a note. Each person can send a limited number of reports a day. After that the tool refuses more, and your client carries on with your task.

Limits#

  • Up to 200 counties per project. Counties with a very large number of parcels make queries slower: create_project returns a notice that says so. import_rows and get_upload_link start a new project in one county only. To add a county to a project, ask MAIA with send_message.
  • Up to 20 city or neighborhood outlines per project. places can name at most 20 distinct cities and neighborhoods that keep their outlines. A neighborhood drawn in several pieces counts each piece. ZIP codes, metros, and regions do not count toward this. For more places, name fewer, or cover their whole counties with the county codes from find_places.
  • SQL reads only the project's own layers. query_project cannot read shared county tables, and it returns at most 1,000 rows. A query over a layer that may hold parcel data spends your workspace's parcel export budget. MAIA's own county records appear only as the own data columns and __sales relations project_schema lists. Licensed property data is never returned. See query_project. For other questions about the data, ask MAIA's agent with send_message.
  • Runs stop at 60 minutes. A run that reaches the limit reports incomplete. Check the project for saved work, then ask MAIA to continue with send_message.