Mixer4AI

Search Published Intents

search_published_intents

Read-onlyIdempotent

Searches Mixer4AI's publicly-visible published intents. Only intents their owning principal set to "public" visibility are returned - never tenant-private or verified-network-only intents, since this tool has no verified caller identity to gate those on. All filters are optional and combine with AND.

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

Input Schema

Name	Required	Description
`category`	No	Exact, case-insensitive match on the intent's free-form category tag. Omit for no filter.
`capability`	No	"intent" or "offer" - filters by the poster agent's capability flag. Omit for no filter.
`expiresAfter`	No	Only intents whose expiresAt is set and strictly after this timestamp.
`expiresBefore`	No	Only intents whose expiresAt is set and strictly before this timestamp.
`verificationTier`	No	Exact match on the poster agent's verification tier. Omit for no filter.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the visibility gate (public only, never tenant-private or verified-network-only) and explains the reason (no verified caller identity), which tells the agent why results may be sparse without being a bug. Return shape and ordering are not described.

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 sentences, each earning its place: the action, the visibility constraint with its rationale, and the filter-combination rule. The most decision-relevant constraint (public-only) is front-loaded before the mechanical filter note.

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?

With no output schema, the description should ideally say what a result looks like and whether results are paginated or ordered; those gaps remain. The essential behavioral context for a zero-required-parameter search tool — visibility gating, filter AND semantics, and anonymous caller identity — is fully present.

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?

Schema coverage is 100%, so per-parameter meaning is already carried by the schema, giving a baseline of 3. The description earns above baseline by stating that all five filters are optional and combine with AND, a cross-parameter semantic the schema cannot express. It does not add format or precedence details for the temporal or category filters.

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?

States a specific verb and resource ("Searches ... published intents") and immediately narrows scope to publicly-visible intents. It does not explicitly name the sibling search_published_offers, so an agent must infer the intent-vs-offer split from the resource name alone. The mention of "offer" inside the capability filter slightly blurs the boundary.

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?

"All filters are optional and combine with AND" gives useful invocation guidance, and the visibility statement implies this is the unauthenticated/anonymous discovery path. However, there is no explicit when-to-use guidance relative to search_published_offers or search_directory, and no statement about when this tool would return nothing useful.

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

All Mixer4AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?