SiteCheck Jobs & Property

Student housing near a university from Student.com

realestate_student

Read-only

Student housing near a university from Student.com (US and Canada): property name, type (PBSA = purpose-built student accommodation, Apartment...), monthly price from/to as listed, rating, distance from the campus in miles, coordinates and listing URL, nearest first, plus the number of properties Student.com maps around that campus. Input = the slugs in Student.com's university URL. Takes about 30 s; allow a 60 s timeout. Related tools on this server, for a different need: realestate_healthgrades when you need Doctors near a US city from Healthgrades' specialty; realestate_hemnet when you need Hemnet homes for sale in an area: address, housing form. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "state": "<state>",
      "city": "<city>",
      "university": "<university>"
    },
    "name": "realestate_student"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City slug, e.g. new-york-city (required)
`limit`	No	Max rows, 1-200 (default 30)
`state`	Yes	State/province slug, e.g. ny (required)
`country`	No	Country slug: us or ca (default us)
`maxPrice`	No	Optional maximum 'from' price per month
`university`	Yes	University slug, e.g. new-york-university (required)

Output Schema

Name	Required	Description	Default
`count`	No
`mapped`	No
`source`	No
`matches`	No
`checkedAt`	No
`properties`	No
`university`	No
`currencyNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real behavioral context: geographic coverage (US and Canada), result ordering ('nearest first'), latency (~30 s, 60 s timeout), per-call pricing with payment rails, and that failed calls are not charged. It stops short of describing pagination or behavior when a campus has no mapped properties.

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?

Front-loaded with the resource and coverage, and every clause carries information (field list, ordering, slugs, timeout, alternatives, price). It is a single dense run-on sentence, which makes it harder to scan than it needs to be, but there is no filler.

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 an output schema present, the description needn't explain return values, yet it does summarize them; the timeout and cost notes cover the operational gaps an agent needs before calling. Remaining gaps are minor: no pagination guidance for the 1-200 limit and no explanation of what maxPrice filters against beyond the schema line.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented with examples, which sets the baseline at 3. The description adds only the provenance of the required slugs (they come from Student.com's university URL) and the country scope; limit, maxPrice, and country defaults get no further explanation beyond 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?

States a specific verb+resource: student housing near a university from Student.com, scoped to US and Canada, and enumerates the returned fields (name, PBSA/Apartment type, price from/to, rating, distance in miles, coordinates, listing URL, campus property count). It also names two sibling tools and the different needs they serve, so an agent can place it without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit input guidance ('Input = the slugs in Student.com's university URL') and a runtime/timeout expectation ('about 30 s; allow a 60 s timeout'), plus routing to realestate_healthgrades and realestate_hemnet for unrelated needs. It does not distinguish this from the closest rental siblings (realestate_apartments_com, realestate_zillow_rentals) or state when not to use it.

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

All SiteCheck Jobs & Property 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?