Web Search Tool on Amazon Bedrock AgentCore vs Arcmira

Web Search Tool on Amazon Bedrock AgentCore

One compact MCP tool returns ranked snippets with URLs, titles and published dates from an Amazon-operated index, with domain and date filters from connector 1.2.0, at $7 per 1,000 queries. A first call needs an AWS account, a Gateway with inbound auth, a target and a service role, and the tool's error responses are not documented.

Arcmira

Four code-mode tools over a documented v1 API, OAuth 2.1 with four scopes, a read-only sign-up key from two API calls and no card, and a 1,000-credit free month. No status page, SLA or security.txt, breaking v1 changes shipped in October with same-day notice, the server is at 0.10.7, and the index covers the shows Arcmira transcribes.

Web Search Tool on Amazon Bedrock AgentCore

1. Call tools/list on the gateway and take the tool's name from it. AWS's call examples name gateway tools by target and tool
2. Keep query to 200 characters and maxResults between 1 and 25 (default 10). The published schema states these limits only in descriptions
3. Check the target's connector version before sending filters. Version 1.1.0, the default, exposes only query and maxResults
4. Keep each result's URL and title with any answer built from it. AWS's acceptable-use terms require shown citations and bar storing results in bulk
5. On a throttled request, wait the retryAfter seconds in the error body. The default quota is 10 Web Search requests a second, adjustable

Arcmira

1. Call arcmira_describe once per session and write one program per question for arcmira_execute_read; return only the fields the answer needs, since output is cut at 12,000 characters and 3,000 per string.
2. Resolve names with arcmira.resolve (free) before any about, by, entity_ids or channel filter; a name in a filter fails with id_required. Plain keyword search needs no resolver call.
3. Check arcmira.status() or GET /v1/me for the plan, scopes and usage.credits.available before metered reads; on Free, media newer than 30 days and pages past the first fail with freshness_requires_paid and pagination_gated.
4. A Premium read of an untranscribed video starts a transcription that uses credits (300 per started 15 minutes) and may return pending; read the same video again later, which is never charged twice, and send retry: true only when the user asks.
5. Over HTTP send Authorization: Bearer arc_sk_..., an Idempotency-Key on every POST and PATCH, honour Retry-After on 429, and switch on error.code, following unlock.url on 402 and 403 rather than re-authenticating.
6. Use arcmira_execute_write only after listing the user's monitors; it creates, follows and pauses but never deletes, and a connection made before server 0.9.0 answers insufficient_scope until reconnected.