Citizen Space MCP server

Get a public activity

get_public_activity

Read-only

Fetch details of a specific published Citizen Space activity by department ID and activity ID. Returns same fields as search results, with option to include contact details.

Instructions

Overview of one published activity by department id and activity id (the two slugs in its URL), from the unauthenticated Public API (json_consultation_details). Same fields as search_public_activities.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dept": "<dept>",
      "id": "<id>"
    },
    "name": "get_public_activity"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Activity ID, e.g. spring-planting-in-kings-gardens
`dept`	Yes	Department ID, e.g. parks-and-recreation
`fields`	No		all
`include_contact_details`	No	Include the activity's contact phone and email and stop redacting text

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine unannotated context: this hits the unauthenticated Public API and is the json_consultation_details endpoint, and that its field set matches the search tool. It doesn't note whether unpublished activities error or that contact data is normally redacted.

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?

A single, dense sentence that front-loads the resource and identity scheme; no filler, no restatement of the title.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, 'Same fields as search_public_activities' usefully signals the return shape, and the URL-slug framing explains how to address the resource. Only the undescribed 'fields' enum parameter remains a gap.

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?

Explains that dept and id are the two slugs appearing in the activity URL, which is more than the schema's example strings convey, linking the parameters to a real-world source. It says nothing about the 'fields' enum parameter, which the schema leaves undescribed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: retrieves one published activity, addressed by department id and activity id (the two URL slugs), from the unauthenticated Public API. The singular 'one' plus 'Same fields as search_public_activities' cleanly distinguishes it from the plural sibling, though it never states the verb explicitly beyond 'Overview'.

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

Usage Guidelines3/5

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

Implicitly routes the agent: use this when you have both slugs and want a single activity, versus search_public_activities for discovery. No explicit when-to-use/when-not or prerequisite statement (e.g. what happens if the activity is unpublished).

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

Deploy Server