Skip to main content
Glama

List property portals

list_sources
Read-only

Call this first to get the exact location format and accepted filters for each source. Lists the portals search_listings can read: country, rent or sale, accepted filters, how to write the location and whether get_listing works for it. Free.

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_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two pieces of context beyond that: it is a zero-argument discovery call, and it is "Free", implying no paid API quota is consumed. It does not describe output shape or size, but the annotation bar is already met.

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 sentences, front-loaded with the imperative "Call this first", and every clause carries payload (format, filters, country, rent/sale, get_listing support). Even the trailing "Free." fragment communicates a real cost trait.

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?

No output schema exists, so the description must characterise the return value, and it does so field-by-field. For a zero-param, read-only discovery tool this covers everything an agent needs to decide to call it and to interpret the result.

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?

With zero parameters the baseline is 4, and the description earns it by instead explaining what the call returns per source (location format, accepted filters, supported operations), which is the only semantics an agent needs here.

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 ("Lists the portals search_listings can read") and reconciles the ambiguous tool name 'sources' with the title's 'portals'. It also enumerates exactly what each entry contains: country, rent/sale, accepted filters, location format, and get_listing support, which distinguishes it cleanly from the two siblings.

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

Usage Guidelines5/5

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

"Call this first" gives explicit sequencing guidance and effectively names the downstream tools (search_listings, get_listing) as the consumers of its output. The condition that selects this tool over the siblings is unambiguous without needing any exclusions.

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.