Tools

Every Wire container ships with 5 tools. These are the same 5 tools on every container, regardless of how much data is inside or what types of content you’ve added.

Tool	Purpose
`wire_explore`	Discover entity types, fields, and relationships
`wire_search`	Query data: list, get, filter, text search, semantic search
`wire_write`	Save an entry to the container
`wire_delete`	Remove an entry by ID
`wire_analyze`	Run an analysis pass to discover entity types and enrich context

Ephemeral containers also have wire_claim for converting to a permanent container.

`wire_explore`

Discover what data is in the container: entity types, their fields and relationships, entry counts, and optionally sample entries. Call this first to understand the schema before searching.

Results will be empty until the container has had at least one analysis pass. Run wire_analyze to build the schema.

Parameter	Type	Required	Description
`entityType`	string	No	Drill into a specific entity type for detailed schema, samples, and available relationships
`includeSamples`	boolean	No	Include sample entries (only when `entityType` is specified). Default `false`.
`sampleLimit`	number	No	Number of sample entries to return (1-10). Default 3.

Example usage:

What kind of data is in this container?

The agent calls wire_explore with no parameters. Wire returns all entity types, their field names, and record counts. The agent can then drill into a specific type:

Show me the fields and a few examples from the NPS Responses.

The agent calls wire_explore with entityType: "NPS Response" and includeSamples: true.

`wire_search`

Find and retrieve data from the container. Supports five retrieval modes, all through a single tool.

Parameter	Type	Required	Description
`mode`	string	Yes	Retrieval mode: `list`, `get`, `filter`, `text`, `semantic`
`entityType`	string	Required for list/get/filter/text	Entity type to query. Use `wire_explore` to discover available types.
`id`	string	No	Record ID (get mode only)
`query`	string	No	Search query (text and semantic modes)
`filters`	array	No	Field filters with operators (filter mode)
`fields`	string[]	No	Return only these fields (projection)
`include`	string[]	No	Related entity types to include. Use `wire_explore` to see relationships.
`orderBy`	object	No	Sort by field and direction
`limit`	number	No	Max results (default 100, max 1000)
`offset`	number	No	Pagination offset
`topK`	number	No	Number of semantic results (semantic mode, default 5, max 100)
`minScore`	number	No	Minimum similarity score 0-1 (semantic mode)

Modes

list — Browse records of an entity type with pagination.

get — Retrieve a single record by ID. Includes mentions of this record in other entries.

filter — Find records matching field conditions. Each filter has a field, operator (eq, neq, gt, gte, lt, lte, contains, in), and value.

text — Full-text keyword search across records of an entity type.

semantic — AI-powered vector search across all entries. Finds relevant content even when exact keywords don’t match. Does not require entityType.

Example: NPS Survey Data

After uploading a CSV file with NPS survey responses and running analysis:

Response_ID,Customer,Plan,Survey_Date,NPS_Score,Category,Feedback_Text
NPS-3000,Anonymous,Free,2025-11-05,4,Detractor,Switched to competitor. Better features.
NPS-3001,Anonymous,Enterprise,2025-09-01,8,Passive,Works well but needs more features.
NPS-3009,Acme Corp,Free,2025-11-08,9,Promoter,Best tool for AI context management.
...

Your agent discovers the schema with wire_explore, then queries the data with wire_search:

Show me all detractor responses from Enterprise customers.

The agent calls wire_search with mode: "filter", entityType: "NPS Response", and filters for Category = "Detractor" and Plan = "Enterprise".

Find any feedback mentioning pricing concerns.

The agent calls wire_search with mode: "semantic" and query: "pricing concerns". This finds entries using phrases like “too expensive” or “not worth the cost” even without the word “pricing.”

`wire_write`

Save an entry to the container.

Parameter	Type	Required	Description
`content`	string or object	Yes	The entry content. Strings are stored as text. Objects are stored as structured data.
`tags`	string[]	No	Tags for categorization and filtering
`metadata`	object	No	Arbitrary key-value metadata
`source`	string	No	Where this entry came from. Defaults to `"agent:mcp"`.

Example usage:

Save a note about the customer meeting with Acme Corp today.
They want to upgrade to Enterprise and need SSO support.

The agent calls wire_write with the meeting notes as content, tagged with ["meeting", "acme-corp"].

`wire_delete`

Remove an entry by its ID.

Parameter	Type	Required	Description
`entryId`	string	Yes	The ID of the entry to delete

`wire_analyze`

Trigger an analysis pass on the container. Takes no parameters.

Each pass examines a portion of the container’s entries, discovering entity types, relationships, and enriching context. Run analysis regularly as you add or change content. Over time, repeated passes build a complete and consistent schema available through wire_explore and wire_search.

`wire_claim`

Generate a claim link for an ephemeral container. Takes no parameters. Returns a URL that the user can open in a browser to sign up or log in and claim the container permanently.

Claim links are short-lived. Call wire_claim again to generate a new one if needed.

This tool only appears on ephemeral containers (created via instant onboarding). Once a container is claimed and belongs to a permanent organization, wire_claim is no longer listed.

Example usage:

I want to keep this container. Can you generate a claim link?

The agent calls wire_claim and returns a URL. The user opens it, signs up or logs in, and the container is moved into their organization.

Listing and Unlisting Tools

You can list or unlist individual tools from the container settings in the Wire dashboard. Unlisted tools are hidden from MCP clients and cannot be called.

Next Steps

Core Concepts - Learn about entries and containers
MCP Overview - How to connect and use tools