Skip to main content
Glama

Neofort IMO — ansambluri rezidențiale București

Search articles

search_articles
Read-onlyIdempotent

Search the Neofort IMO blog (Romanian) about buying property in Bucharest: taxes, VAT, mortgages, legislation, short-term rental, owners associations, neighbourhoods. Returns title, summary, dates and links; read the "markdown" link for the full text. Without a query, returns the latest articles.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 5).
queryNoTopic keywords, ideally in Romanian, e.g. "impozit locuinta", "TVA apartament nou", "regim hotelier".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed world), so the bar is lower, and the description still adds value: the fields returned (title, summary, dates, links), the need to follow the 'markdown' link for full text, and the empty-query fallback behavior. It omits anything about result ranking or relevance behavior, keeping it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose in the first clause, followed by the topic list, then return fields and the fallback behavior. The topic enumeration is long but genuinely helps query formulation; otherwise there is no wasted wording.

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?

For a two-parameter read-only search with no output schema, the description covers the domain, the language expectation, the returned fields, how to get full text, and the no-query case. The only mild gap is relevance/ordering behavior, which is minor for this tool.

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 both parameters are already documented in the schema, including the limit default and max. The description adds topic guidance and the no-query behavior for the query parameter, but does not add syntax or matching semantics beyond that, which fits the baseline 3.

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 (Search) and resource (articles on the Neofort IMO blog) plus the topical scope (Romanian content on buying property in Bucharest: taxes, VAT, mortgages, legislation, rentals, owners associations, neighbourhoods). This clearly separates it from search_apartments, which by name targets listings rather than editorial content.

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?

The description gives a clear operational cue: 'Without a query, returns the latest articles,' which tells the agent how to use the tool for browsing vs. targeted lookup. It also directs the agent to read the 'markdown' link for full text. It stops short of naming an explicit alternative tool to use instead, so it does not reach the top band.

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