Skip to main content
Glama

Neofort IMO — ansambluri rezidențiale București

Get project details

get_project
Read-onlyIdempotent

Full details of one Neofort IMO residential project: description, every apartment type with prices and availability (sold units are marked), parking, amenities, distances to metro/schools/shops, FAQ and broker. Works for projects on sale and for sold projects in the portfolio. Accepts the slug, "Neofort 84", "84" or part of the name.

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": {
      "project": "<project>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject slug, number or name, e.g. "neofort-84-titan-pallady" or "Neofort 84".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is settled. The description adds genuinely non-structural context: sold units are marked in the availability data, and the tool also resolves projects that are already sold out rather than erroring on them.

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 tightly packed sentences with no filler, and the identity/scope statement is front-loaded. The first sentence is a long comma-separated inventory of returned fields, which is dense but still scannable.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of describing the return payload, and it does so field-by-field while also covering the sold-project edge case and input flexibility. Nothing an agent needs in order to call this single-parameter read correctly is missing.

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?

Schema coverage is 100%, so the parameter is already documented. The description still adds meaning beyond the schema by spelling out the concrete accepted forms — the slug, 'Neofort 84', the bare number '84', or a partial name — which tells the agent it can be loose with input.

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 and resource ('Full details of one Neofort IMO residential project') and enumerates exactly what comes back: description, apartment types with prices and availability, parking, amenities, distances, FAQ and broker. The 'one project' scoping cleanly separates it from list-oriented siblings such as list_projects.

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?

Explicitly states the applicability condition that matters most ('Works for projects on sale and for sold projects in the portfolio'), which is real guidance an agent would otherwise have to guess. It stops short of naming when to prefer a sibling like search_apartments instead, so no exclusions are offered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources