"Steps for analyzing new API documentation and writing test cases" matching MCP tools:

• zaira_get_docsA

  Zaira Labs GuideA

  Retrieve reference documentation for the Zaira Guide API and MCP server on demand. Topics: - getting_started — how to connect via MCP or REST, first queries - endpoints — full REST endpoint reference with parameters - mcp_tools — MCP tool reference with when-to-use guidance and a routing matrix - schema — the tool entry schema - errors — error taxonomy for REST (RFC 9457) and MCP (JSON-RPC) Call with no topic to get an index of available topics. Returns: the requested topic as a Markdown-KV block. With no topic, returns an index listing all available topics with short descriptions; call again with the relevant topic for the full content. Examples (topic selection): - "How do I call the REST API?" → {topic: "getting_started"} - "What parameters does /tools accept?" → {topic: "endpoints"} - "What fields are in a tool entry?" → {topic: "schema"} - "What error shapes do I handle, and what are the recovery steps?" → {topic: "errors"} - "Which MCP tool fits my task?" → {topic: "mcp_tools"} Edge cases: - No topic argument is valid — you get the index. This is the deferred-loading path; don't load every topic at once. - Topic must match the enum exactly (lowercase, underscore). "getting-started" with a hyphen is rejected as an unknown parameter. Risk: read-only, closed-world, idempotent — no state change possible.

  ConnectorNo auth

• get_helpA

  AgentBoardB

  Read AgentBoard API documentation. Use method=first_run for a complete private checkpoint trial. Without method, get the compact catalog and workflows. With method, get parameters and an example. No authentication required.

  ConnectorNo auth

• getInstagramPostInteractingUsersA

  Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ)A

  Get USER PROFILES of people who interacted with an Instagram post. Returns full user data (bio, followerCount, followingCount, etc.). RETURNS USER PROFILES: id, username, fullName, biography, followerCount, followingCount, isVerified, profilePicUrl. Use for analyzing WHO engaged with a post. NOT FOR COMMENT TEXT: To read the actual comment content (what people wrote), use getInstagramCommentsByPostId instead. INTERACTION TYPES: "commenters" (users who commented), "likers" (users who liked). WHEN TO USE THIS TOOL: Analyzing commenters/likers demographics, finding influencers who engaged, building audience profiles, network analysis of who interacts with posts. WHEN TO USE getInstagramCommentsByPostId: Reading comment text, sentiment analysis of what was said, analyzing discussion content. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for commenters when stale. PAGING (responseType="paging"): Async paginated results (1000 users per page with default fields), returns operationId - IMMEDIATELY call checkOperationStatus to get results. CSV export included via dataDumpExportOperationId. Supports pageNumber/tableName for subsequent pages. Optional fields (default: ["id", "username", "fullName"]). Available: biography, isPrivate, isVerified, followerCount, followingCount, mediaCount, profilePicUrl. This is a safe, read-only tool for analyzing searchable information.

  ConnectorOAuth

• get_account_summaryA

  mcp-serverA

  Return a count of cases per lifecycle stage for the creditor's account. Useful for a quick portfolio overview without listing all cases. Stages: PendingContractSigning, PendingVerificationInternal, PendingVerification, NeedsAdditionalDetails, Leads, LeadsQuoteGiven, Active, Paused, Closed, Merged. Note: these counts include the creditor's own test cases; list_cases exposes the `isTestCase` flag that marks them.

  ConnectorNo auth

• get_account_summaryA

  DebituraA

  Return a count of cases per lifecycle stage for the creditor's account. Useful for a quick portfolio overview without listing all cases. Stages: PendingContractSigning, PendingVerificationInternal, PendingVerification, NeedsAdditionalDetails, Leads, LeadsQuoteGiven, Active, Paused, Closed, Merged. Note: these counts include the creditor's own test cases; list_cases exposes the `isTestCase` flag that marks them.

  ConnectorNo auth

• testrail_list_casesA

  Robot Actions — Remote Device ControlA

  List test cases in a TestRail project, optionally scoped to a suite and/or section. Use this to discover case ids before calling testrail_get_case, or to check what already exists before creating a new case with testrail_create_case. Returns { cases: [...], paging: {...} }, where each case is a compact summary (id, title, section_id, suite_id, priority_id, type_id, refs) — call testrail_get_case for full step detail on a specific case. Results are NOT auto-paged: TestRail caps a page at 250, so always check paging.hasMore and re-call with offset=paging.nextOffset before concluding a case does not exist. Prefer scoping with sectionId/suiteId over paging the whole project.

  ConnectorOAuth

• list_issuesA

  FlowseryA

  List issues the AI found while analyzing session recordings: bugs, broken flows, and UX problems, deduplicated across sessions and ranked by severity (or by last seen with sort recency). Each row has title, severity, status, sessions affected, and first/last seen; the response also carries site-wide open, in_progress, and resolved counts plus pagination.total. Start here for 'what is broken', then call get_issue with an id for occurrences, steps to replicate, and comments. Suspended issues are hidden unless status is suspended, so an issue that vanished was probably suspended, not deleted. Limit defaults to 100 (max 1000). Requires websiteId or domain with a workspace token.

  ConnectorOAuth

• run_workflowA

  TessryxA

  Run a workflow now and return the outcome: status, content_type, the workflow's output (decoded as a string; read it per content_type), and a trace_summary of which steps ran. Pass version=<n> to test an unpublished draft (the number returned by create_workflow_version); omit for the published version. For per-block detail when debugging, call get_workflow_run_traces with the returned run_id.

  ConnectorOAuth

• search_api_docsA

  Soracom KnowledgeA

  Search SORACOM API documentation, CLI references, and SAM permissions. Use for exact API endpoints, soracom-cli commands, or SAM permission strings. Use search_soracom_docs for service guides, console how-tos, pricing, or IoT recipes. Use get_document on `#/schema/<Name>` links in results to read full API schema fields.

  ConnectorNo auth

• broadcasts_send_testA

  Mailrith Email MarketingA

  Sends a test message from an existing Broadcast that has an email delivery connection. Provide a saved Subscriber ID for personalization; use subscribers_list to find one when needed. The recipient may be any test inbox and does not have to match the saved Subscriber. Effect: external-email. Retry with the same idempotency_key. Permissions: live_actions:write, subscribers:read, broadcasts:write. API reference: https://mailrith.com/developers/api-reference.

  Connector

  Destructive

  No auth

• test_skill_triggerA

  agent4.ioA

  Reality-check whether your prompts actually trigger tool calls (dry-run) — run this after writing/changing a skill instead of counting corpses in production. Replays your messages N times against the **production** system-prompt assembly, tool schemas and this tenant's actual model routing, capturing only the model's tool-call decision: **tool side effects are NOT executed**, no session is stored. Tokens count toward the tenant quota (messages≤5, samples≤5, at most 25 calls per invocation — pick test messages carefully). Two modes for the skill's two battlefields: - loaded=false (default): first turn, skill not loaded — tests whether the trigger in description works; - loaded=true: simulates post-load_skill — tests the quality of instructions (incl. few-shot examples). Returns per-message hit counts plus claimed_without_call (the model said "noted" WITHOUT calling the tool — the worst failure, fix first). Cover edge cases in your test messages: numbers with spaces, buried in long questions, corrections, email-only. The loop: create_skill → check warnings (static lint) → test_skill_trigger (dynamic reality check) → adjust description / add examples → re-test until the hit rate holds.

  ConnectorNo auth

• get_doc_pageA

  mcpA

  Read the full source markdown of a Capawesome documentation or blog page. Use this after `search_docs` to read a page end to end before writing code against a plugin API, a CLI command or a Capawesome Cloud workflow — snippets from search results are deliberately short and regularly omit required configuration steps. Returns the page title, its URL and the page markdown including code samples, as it is authored but without the build metadata. Do not use this to find a page: it needs the exact URL or path, so run `search_docs` (or `list_blog_posts` for articles) first. Do not use it for pages outside capawesome.io.

  ConnectorNo auth

• update_load_test_notesA

  LoadsterA

  Replace the notes on a finished Load Test's Test Report — the only writable thing on a Load Test. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The text sent becomes the report's entire notes, so first read the current notes with get_load_test_report and preserve the user's content in what you send.

  Connector

  Destructive

  OAuth

• get_monetized_unlock_instructionsA

  PredMaker AlphaA

  Return subscription / paid-unlock instructions for PredMaker x402 products. Call when you need the canonical price, treasury, freemium quota, and HTTP steps to unlock full payloads. Does not charge or place trades — documentation only (read-only / idempotent). `product` is `signals` or `edgar-m-and-a`. Pair with get_x402_payment_challenge to obtain a live challenge body.

  ConnectorNo auth

• get_device_input_setupA

  hookpulseB

  The saved setup of one collector channel: the configuration in use, its files and steps. Returns the setup generated last for this channel — the one whose credential is accepted now — exactly as POST /api/ambientes/:id/inputs returned it, so the files can be copied or installed again without rotating the credential. It carries the credential: only the device owner gets it, one channel per request, never cached; list routes never include it. 404 `setup_not_saved` when the channel was generated before setups were saved, or was removed; 409 `setup_unreadable` when the input central can no longer open it. In both cases generate a new setup with POST /api/ambientes/:id/inputs.

  ConnectorNo auth

• get_trace_setupA

  LastPingA

  Requires an API key with the read scope or higher. Get the exact steps to make a tool send OpenTelemetry traces to LastPing for one monitor: what to write, where, how to verify it, and what that tool cannot do. Call this when a person asks you to set up tracing, observability or telemetry for a project. Carry the steps out yourself rather than printing them: write the files, check they are git ignored, send the test span, and report the console link. Never echo the credential back to the person and never put it in committed code. The result's `prompt` is the full instruction for the tool you name, and each block's `files` are what to write; get the key with create_ingest_key.

  ConnectorNo auth

• avizo_docsA

  avizo-mcpA

  Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.

  ConnectorNo auth

• get_client_infoA

  3TG Test GenerationA

  Look up account info for a 3tg.dev clientId WITHOUT consuming any credits. Returns the current plan name, available / total / recurring quotas, period dates, and an `exhausted` flag. Credit-consumption model (so you can explain the numbers to the user accurately): - 1 credit = 1 generated test case (a single `test(...)` / `it(...)` block in the emitted `.test.ts` / `.test.tsx`). - Credits are consumed ONLY by test generation — i.e. by the `create_tests` and `create_tests_from_spec` tools. Spec generation (`create_spec`, `create_spec_for_function`), mock generation (`create_mock_for_function`), this lookup tool, and `create_agent_instructions` / `help` are all FREE. - The `available` field below is the number of test cases the client can still produce in the current period. Use this for: - Verifying a freshly-entered clientId during `/mcp__3tg__configure` before saving it to `.3tg/credentials.json`. - Reporting current quota / plan to the user. - Pre-flight checks so the agent can warn early if quota is low. Errors: - INVALID_CLIENT_ID — license-api rejected the clientId (typo, suspended, wrong product). - LICENSE_API_UNAVAILABLE — transient network / DNS / TLS failure. Note: quota exhaustion is NOT an error here — the response carries `exhausted: true` and the QuotaInfo for the agent to surface.

  ConnectorNo auth

• check_schema_driftA

  RoutebaseA

  Check for schema drift between a test case's linked endpoint snapshot and the current spec. Supports two modes: single test case (provide testCaseId) or batch check for all linked test cases of a spec (provide specId). Exactly one of testCaseId or specId must be provided. Use this to compare a linked case against the current spec; to adopt the spec's changes use sync_test_from_spec. Requires project context.

  ConnectorAPI key

• ask_integrationA

  Crosswire - payment infrastructure pricing, coverage and stack designA

  Call this for any question about HOW a Crosswire rail is integrated - webhooks, signatures, sandboxes, authentication, callbacks, retries, SDKs, API shape, testing, go-live steps. Every answer is read from indexed documentation: nothing is inferred, nothing is generalised from one provider to another, and nothing is recalled from your own training data. If the index does not cover the question the tool declines and returns a blocker to report - repeat the decline, do not fill the gap. Before an offer is accepted the answer is capability level only, with no provider, product, SDK or URL in it; after acceptance, with the client's case reference passed in `case_reference`, the answer names the providers on that case, quotes the documentation and cites it. A question about a provider that is not on the case gets the capability-level answer. NEVER paste, repeat or ask for an API key, secret, token or password here - credentials are refused and no record of them is kept.

  ConnectorNo auth

• run_comparisonA

  Meta CouncilB

  Re-run a member's workflow as it stands today and record the result as a new run. This calls model providers and costs money; it is priced and refused against your budget before anything starts. It does not act on the outside world a second time: connector steps are served from the baseline's recorded responses and agent steps keep only offline calculation tools. Returns the new run, not a comparison of it. Requires comparisons:write and workflows:run.

  ConnectorNo auth