UniAffitti Room Finder

Create a listing

create_listing

Create a listing draft for UniAffitti moderation. It is not public until approved. The draft stores the full property address and coordinates; university and campus IDs remain unset. Do not include passwords, payment-card details, government identifiers, health or biometric data in the description.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes
`title`	Yes
`features`	No
`latitude`	Yes	Exact latitude of the property being listed.
`longitude`	Yes	Exact longitude of the property being listed.
`room_type`	Yes
`description`	Yes	Describe the room and rental terms only. Do not include passwords, payment-card details, government identifiers, health or biometric data.
`address_full`	Yes	Full address of the property being listed; shared with the connector when you create this listing.
`country_code`	Yes	ISO 3166-1 alpha-2 country code.
`price_monthly`	Yes
`property_type`	No		apartment
`available_from`	No	YYYY-MM-DD.
`deposit_amount`	No
`location_label`	No
`price_currency`	No		EUR
`property_floor`	Yes
`min_stay_months`	No
`occupancy_status`	No		available

Output Schema

TableJSON Schema

Name	Required	Description	Default
`room_id`	Yes
`location`	Yes
`next_step`	Yes
`moderation_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 7, 2026

addedInput schema / properties / address_full / description

Added value: +"Full address of the property being listed; shared with the connector when you create this listing."

addedInput schema / properties / description / description

Added value: +"Describe the room and rental terms only. Do not include passwords, payment-card details, government identifiers, health or biometric data."

addedInput schema / properties / latitude / description

Added value: +"Exact latitude of the property being listed."

addedInput schema / properties / longitude / description

Added value: +"Exact longitude of the property being listed."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "location": {
+      "additionalProperties": false,
+      "properties": {
+        "city": {
+          "type": "string"
+        },
+        "country_code": {
+          "type": "string"
+        },
+        "location_label": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "city",
+        "country_code",
+        "location_label"
+      ],
+      "type": "object"
+    },
+    "moderation_status": {
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "room_id": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "room_id",
+    "moderation_status",
+    "location",
+    "next_step"
+  ],
+  "type": "object"
+}

AddedAug 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, non-idempotent, openWorld). The description adds real context beyond that: the object is a draft, invisible until approved, stores full address and coordinates, leaves university/campus IDs unset, and carries a PII prohibition. It does not touch idempotency (duplicate drafts on re-call), which the annotation covers.

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?

Three tight sentences, front-loaded with the create action and draft state, followed by storage behavior and the compliance constraint. No filler, though the PII sentence duplicates the schema's description-field note.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the moderation/draft lifecycle is covered. However, for an 18-parameter create tool with low schema coverage, the description omits guidance on most inputs and on re-call/idempotency behavior, leaving a noticeable gap.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% across 18 parameters (10 required, 3 enums), so the description must compensate heavily and does not. It speaks only to address_full, coordinates, and an out-of-schema note about university/campus IDs; price_currency, room_type, occupancy_status, property_type, and other required fields get no added meaning, and the PII advice for description merely repeats the schema.

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 names a specific verb (Create) and resource (a listing draft) and scopes it to a named workflow (UniAffitti moderation). No sibling tool creates listings, so it is unambiguously distinguishable from create_rental_request and the list/update siblings.

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?

It clarifies that the result is a non-public draft pending approval, which implies when this is appropriate, but it never states when to use this over an alternative or any prerequisite for calling it. With no explicit alternative named, usage must be inferred.

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

All UniAffitti Room Finder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?