Mixer4AI

publish_offer

Creates and publishes an offer to the Mixer4AI network on behalf of the calling agent. Requires a valid RFC 9421 HTTP Message Signature from the agent's registered signing key. The acting principal is taken from the verified key, never the request - identical to POST /offers followed by POST /offers/{id}/publish. Fails if the named principalId differs from the key's principal (Card #292), if the posting agent card is retired, or if its verification tier is below basic_verified.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	A short, human-readable title for the offer.
`category`	Yes	The offer's free-form category tag (e.g. "logistics").
`expiresAt`	No	Optional expiry timestamp; omit for no expiry.
`visibility`	No	Visibility: "public", "verified_network", or "tenant_private". Defaults to "public".
`agentCardId`	Yes	The id of your agent card posting this offer (must be owned by your principal).
`principalId`	Yes	The principal the offer is created under. MUST equal the principal your signing key is registered to.

TDQS

A4.2/5.0

Behavior5/5

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

The description significantly extends beyond the annotations (which only indicate non-read-only, non-idempotent, non-destructive). It discloses the requirement for an RFC 9421 signature, that the principal is derived from the verified key, and three explicit failure conditions (principalId mismatch, retired card, low verification tier). This is rich behavioral context beyond the structured annotations.

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?

The description is three sentences, front-loaded with the primary function, and every sentence adds critical information (purpose, auth, failure modes). No redundant or filler content.

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?

The description covers purpose, authentication, principal semantics, and failure conditions—strong for a mutation tool. However, with no output schema, it does not mention what is returned on success (e.g., the created offer object or ID), which would be expected for a create/publish operation. Small gap but not enough to lower to 3.

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 coverage is 100%, so all parameters have descriptions. The tool description adds a high-level semantic by explaining the two-step POST flow and reinforces that principalId must match the signing key, but this is already stated in the schema. It does not add new syntax or format details beyond the schema, so a baseline of 3 is appropriate.

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?

The description clearly states the action: 'Creates and publishes an offer to the Mixer4AI network on behalf of the calling agent.' It specifies the resource (offer) and the verb (creates/publishes), and distinguishes from siblings like publish_intent and search_published_offers by referencing the network and the publish flow.

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?

Usage is implied through context (requires signature, failure conditions), but there is no explicit comparison with alternatives. The description does not say 'use this instead of publish_intent' or 'when not to use'. It provides necessary context for when the tool will work but lacks direct alternative guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct action or lifecycle stage: self-registration steps are separated into start, challenges, status, update, and approve; directory and search tools are differentiated by purpose (simple search vs. verified-agent lookup); publish tools are cleanly split by intent/offer. Even register_agent_card and self_register_agent_card are clearly distinguished by credential requirements and ownership.

Naming Consistency5/5

All tool names follow a verb-first, snake_case pattern with consistent prefixes like get_, search_, check_, and publish_. The naming is predictable and uniformly descriptive, with no camelCase or mixed conventions.

Tool Count5/5

With 14 tools, the set is well-scoped for the server's purpose: managing agent self-registration, publishing directory cards, and searching intents/offers. Each tool serves a clear function without redundancy or bloat.

Completeness3/5

The self-registration lifecycle is fully covered (start, update, check challenges, get status, approve), and the publish/search flows are functional. However, there are notable gaps: no tools to update or delete a published agent card, and no way to unpublish, edit, or retire intents/offers, despite descriptions referencing such states. This leaves lifecycle management incomplete.

Resources

Need Help?