Skip to main content
Glama

Neofort IMO — ansambluri rezidențiale București

Get contact details

get_contact
Read-onlyIdempotent

How to reach Neofort IMO: phone, WhatsApp, email, office address, opening hours and contact form. With a project, also the broker in charge of it and their phone. Use this to send the person to a human for a firm offer, a viewing or a reservation — this server cannot send requests.

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": "get_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoOptional project slug, number or name, to get its broker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-open-world and non-destructive, so safety is covered. Beyond that the description discloses the returned payload contents and a conditional behavior (supplying a project also returns the broker in charge and their phone), plus a functional boundary — it cannot send requests — which an agent would otherwise have to discover by failing.

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?

Three short sentences, front-loaded with the resource contents, then the conditional behavior, then the usage constraint. No filler and nothing repeated from the title.

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?

With no output schema, the description carries the burden of explaining what comes back and does so by enumerating the contact fields and the conditional broker addition. Combined with the explicit no-send limitation, an agent has everything needed to call it and set expectations correctly.

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% and the single optional 'project' parameter is already documented, so the schema baseline applies. The description adds only that the parameter yields the broker in charge and their phone, which is a modest gain over the schema's 'to get its broker'.

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 the exact resource returned (phone, WhatsApp, email, office address, opening hours, contact form) plus the conditional broker lookup, which is far more specific than the name 'get_contact' alone. It also disambiguates against the surrounding catalog, which is full of project/apartment search tools, by making clear this is company/person contact data rather than a project record.

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?

It gives a concrete when-to-use case — hand the person off to a human for a firm offer, viewing or reservation — and a clear when-not/limitation: the server cannot send requests. It does not name any sibling or state what other tool to call first, but no sibling in this catalog overlaps, so the guidance gap is small.

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