Server Details
Provides access to Civic Plus - See Click Fix, allowing you to interact with your data via an LLM.…
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
15 toolsacknowledgeIssueTry in Inspector
Acknowledge an issue in SeeClickFix with a comment
| Name | Required | Description | Default |
|---|---|---|---|
| comment | Yes | The acknowledgment comment | |
| issueId | Yes | The ID of the issue to acknowledge |
addCommentTry in Inspector
Add a comment to an issue in SeeClickFix
| Name | Required | Description | Default |
|---|---|---|---|
| comment | Yes | The comment text to add | |
| issueId | Yes | The ID of the issue to comment on |
changeLocationTry in Inspector
Change the location of an existing issue in SeeClickFix
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | New latitude coordinate for the issue | |
| lng | Yes | New longitude coordinate for the issue | |
| address | Yes | Street address of the new location | |
| issueId | Yes | The ID of the issue to update location |
closeIssueTry in Inspector
Close an issue in SeeClickFix with a closing comment
| Name | Required | Description | Default |
|---|---|---|---|
| comment | Yes | The closing comment | |
| issueId | Yes | The ID of the issue to close |
createIssueWithDetailsTry in Inspector
Step 3 of 3 when creating a new issue. Use the information collected from the user to create the issue.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | Latitude coordinate (required) | |
| lng | Yes | Longitude coordinate (required) | |
| address | Yes | Street address where the issue is located | |
| answers | Yes | Answers to the request type questions (key-value pairs where keys are question IDs) | |
| deviceId | No | Device ID for tracking | |
| mediaUrl | No | URL of media attachment | |
| reporterName | No | Name of the person reporting the issue | |
| reporterEmail | No | Email address of the person reporting the issue | |
| requestTypeId | Yes | ID of the request type for this issue |
flagIssueTry in Inspector
Flag an issue as inappropriate or problematic in SeeClickFix
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | The reason for flagging the issue (e.g., 'inappropriate', 'spam', 'duplicate', 'not_an_issue') | |
| comment | No | Additional comment explaining why the issue is being flagged | |
| issueId | Yes | The ID of the issue to flag |
followIssueTry in Inspector
Follow an issue to receive notifications about updates in SeeClickFix
| Name | Required | Description | Default |
|---|---|---|---|
| issueId | Yes | The ID of the issue to follow |
getCommentsTry in Inspector
Get all comments for a specific issue in SeeClickFix
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (default: 1) | |
| issueId | Yes | The ID of the issue to get comments for | |
| perPage | No | Number of comments per page (default: 20) |
getCurrentTimeTry in Inspector
Get the current date and time
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
getIssueTry in Inspector
Get a single issue by its ID from SeeClickFix
| Name | Required | Description | Default |
|---|---|---|---|
| issueId | Yes | The ID of the issue to retrieve |
getIssuesTry in Inspector
Get a list of issues from SeeClickFix with optional date filtering
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (default: 1) | |
| endDate | No | End date for filtering issues ISO 8601 format (e.g., "2024-07-28T00:00:00Z") | |
| perPage | No | Number of issues per page (default: 20) | |
| startDate | No | Start date for filtering issues ISO 8601 format (e.g., "2024-07-28T00:00:00Z") |
getRequestTypeDetailsTry in Inspector
Step 2 of 3 when creating a new issue. Use the information requirements that are returned to prompt the user for that information.
| Name | Required | Description | Default |
|---|---|---|---|
| requestTypeId | Yes | The ID of the request type |
getRequestTypesTry in Inspector
Step 1 of 3 when creating a new issue. The user must provide a location to get the request types available in that area.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | Latitude coordinate of the location | |
| lng | Yes | Longitude coordinate of the location |
reopenIssueTry in Inspector
Reopen a closed issue in SeeClickFix with a comment
| Name | Required | Description | Default |
|---|---|---|---|
| comment | Yes | The reopening comment | |
| issueId | Yes | The ID of the issue to reopen |
updateIssueTry in Inspector
Update an existing issue in SeeClickFix
| Name | Required | Description | Default |
|---|---|---|---|
| issueId | Yes | The ID of the issue to update | |
| priority | No | New priority for the issue | |
| assigneeId | No | ID of the user to assign the issue to | |
| categoryId | No | ID of the category to assign the issue to |
FAQ
How do I claim this server?
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
What are the benefits of claiming a server?
- Control your server's listing on Glama, including description and metadata
- Receive usage reports showing how your server is being used
- Get monitoring and health status updates for your server