Robin Saige we check the tools AI agents call

Tu Lugar

com.tulugar/tulugar

Search and manage Paraguay & LatAm real estate from any AI assistant.

— the operator's own registry description reported

Publisher com.tulugar · first seen 2026-08-12 · endpoint https://tulugar.com/api/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
39
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 39 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (3 attempts unverifiable, 0 disagreements)

Cluster rich-solo · distinctiveness 0.395 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency133 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools39
vs populationhigh
capabilities2
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_c86e66f48bf85c9bbf944fca · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public22serves public factstruth-checkable against a public source — the V-ladder applies in full
action14changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative2creates contentno answer key exists; disclosure + stability checks, never truth verdicts
computational1deterministic transformsself-checkable by re-computation and known-answer tests

Tools last seen observed

account_status buy_promotional_credits close_listing closing_costs connect_account create_lead create_listing delete_saved_search edit_listing fetch get_agent get_company get_guide get_listing get_market_summary get_project get_str_data link_email list_locations mortgage_calculator my_inquiries my_listings my_saved_searches neighborhood_guide open_web_session promote_listing publish_listing rental_yield reply_to_inquiry save_search search search_agents search_companies search_listings search_projects send_whatsapp_verification share_listing_whatsapp upload_listing_image verify_whatsapp_code

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific39/39
has a description39/39
description is substantive38/3938/39
parameters are typed39/39
parameters are described25/3925/39

39 of 39 tools graded · 39 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not yet confirmed — 3 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-duty6109.10.00unverifiableus-hts
tariff-duty8471.30.01unverifiableus-hts
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.8.1
server version tulugar

Capabilities: resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:36Zok_tools2001332025-06-18
2026-08-12T05:33:50Zok_tools200402025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.tulugar/tulugar.svg)](https://robinsaige.com/s/com.tulugar/tulugar)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview