Skip to main content
Glama

Neofort IMO — ansambluri rezidențiale București

List projects

list_projects
Read-onlyIdempotent

List all Neofort IMO residential projects currently on sale (zone, stage, room types, starting price in EUR excl. VAT, available units). Optionally also the sold projects from the portfolio, as track record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneNoOptional area or sector filter.
include_soldNoAlso list sold projects from the portfolio (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real value by disclosing what the response contains (zone, stage, room types, starting price in EUR excl. VAT, available units) and that sold projects are excluded unless explicitly requested. It says nothing about ordering or pagination, which keeps it from a 5.

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?

Two compact clauses, front-loaded with the primary listing scope before the optional sold-portfolio mode. The parenthetical field list is dense but each item earns its place by telling the agent what comes back.

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, the description carries the burden of describing returns and does so via the field enumeration. For a zero-required-parameter read tool this is nearly complete; only ordering/pagination and result-size expectations are absent.

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 coverage is 100%, with both parameters already documented in the schema, so the baseline is 3. The description reinforces the meaning of the zone filter and the include_sold default but adds no format, allowed-value, or matching semantics beyond what the schema states.

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?

A specific verb and resource ('List all Neofort IMO residential projects') with scope qualifiers ('currently on sale', plus an optional sold-portfolio mode) and a parenthetical enumerating the returned fields. It implicitly differentiates itself from the singular get_project and from search_apartments, but never names an alternative, so it falls just short of 5.

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?

Usage is only implied: the description establishes that the default listing covers projects on sale and that sold projects are an opt-in extra 'as track record'. It gives no explicit conditions for choosing this tool over get_project or search_apartments, nor when to set include_sold.

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