Zambo

Scam Check

scam_check

Read-onlyIdempotent

Check plain text or a wallet, contract, domain, or URL for scam and phishing indicators. URLs and wallet addresses in supplied text are checked with SCAMRA threat intelligence; EVM wallets may also receive an optional Criptic cross-reference. Returns clean, caution, scam, or unknown with confidence, reasons and sources. A clean lookup is not proof of safety. AER-1 receipt, verifiable offline.

Input Schema

Name	Required	Description	Default
`_ref`	No	Optional handover referral ID from your install link.
`text`	No	Message, email, or other text to check. Embedded URLs and wallet addresses are checked without opening the links.
`chain`	No	Optional chain hint, such as base or monad.
`target`	No	Alias for a single wallet address, domain, or full URL.
`_zambo_key`	No	Optional opaque Zambo access capability. Never place it in a URL or public log.
`_session_id`	No	Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together.
`_caller_label`	No	Optional caller label recorded as a caller-reported claim in the receipt.	zambo-starter
`_caller_handle`	No	Opaque anonymous continuity handle returned during initialize. Reuse it across MCP sessions; it is not payment authorization.
`_continuity_ai_label`	No	Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.

Output Schema

Name	Required	Description
`ok`	Yes
`ids`	Yes
`next`	Yes
`tier`	No
`urls`	Yes
`error`	No
`graph`	No
`active`	No
`result`	Yes	The tool's observed JSON value or plain-text result.
`intents`	No
`next_up`	No
`payment`	No
`day_pass`	No
`today_url`	No
`expires_at`	No
`human_line`	Yes
`next_steps`	No
`daily_recap`	No
`renew_nudge`	No
`unlock_link`	No
`seconds_left`	No
`resume_status`	No
`resumed_result`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- changedOutput schema / properties / human_line / maxLength
```
Previous value: -200New value: +512
```
AddedNov 1, 2026

TDQS

A4/5.0

Behavior5/5

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

The description discloses significant behavior beyond the annotations: embedded URLs and wallet addresses are checked via SCAMRA without opening links, EVM wallets can receive an optional Criptic cross-reference, and results include confidence, reasons, and sources. It also includes an important caveat that a clean lookup is not proof of safety and notes the AER-1 receipt.

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?

The description is front-loaded with the core purpose and remains fairly compact. Some phrasing, such as 'AER-1 receipt, verifiable offline,' is slightly jargon-heavy but still relevant.

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?

Given that an output schema exists and the input schema has full coverage, the description provides complementary context about providers, result categories, and safety caveats. It is complete enough for an agent to understand what the tool does and how to interpret its limits.

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 the schema already explains the parameters in detail. The description adds only the general input scope, not parameter-specific meaning beyond what the schema provides.

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?

The description states a specific verb and resource: checking text or wallet/contract/domain/URL for scam and phishing indicators. It is clear what the tool does, but it does not explicitly distinguish it from sibling tools such as prompt_shield or ghost_audit_site.

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?

The description implies usage by listing acceptable input types, but it gives no explicit when-to-use guidance or alternatives. An agent must infer when to choose scam_check over tools like prompt_shield or ghost_audit_site.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zambo tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.