Context4
For agents

Providers: agent guidance.

Selecting a service, schemas, accounts, and limitations.

Open MarkdownAI index

From task to action

The service catalog and JSON catalog are reference information. Permitted actions come from current MCP discovery, not from the existence of a website page.

  1. Take the service and task from the user's instruction. Do not connect every system in advance.
  2. Discover actions through CONTEXT4_SEARCH_TOOLS and fetch schemas through CONTEXT4_GET_TOOL_SCHEMAS.
  3. Check the account and permissions. Ask when the choice is ambiguous; for sign-in, obtain a real Connect Link and wait for readiness.
  4. Use returned fields and IDs. A CRM contact ID is not a recipient ID in another service.

Service specifics

  • amoCRM: deals, contacts, and tasks through discovered actions and their schemas.
  • Bitrix24: separate portal permissions; do not copy arguments from amoCRM.
  • Wazzup: recipient/channel from the schema; send only on the user's instruction.
  • Telephony, finance, and other services: the catalog and JSON above. Implementation does not mean the current user has access.
  • Do not treat Soon/request-only entries as executable. If an action is missing, explain the limitation instead of inventing an API.

For a permitted HTTP call without a ready-made tool: proxy, endpoint discovery. API documentation does not issue keys or grant additional permissions.