Skip to main content
Glama

Connect: intake source configuration

atisbo_connect
Destructive

WHERE Atisbo gets its signals. Modes: list, catalog, create (returns endpoint), configure, pause, resume, sync_now, delete (soft-disconnect). THE CATALOG IS NOT THE BOUNDARY: almost anything connects — call catalog and read fallback before saying "Atisbo cannot ingest that". Atisbo only READS a connected system. create returns the signing secret shown ONCE — relay to the human immediately.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "atisbo_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomode=create: "email" provisions the ingest address; default webhook.
modeNolist/catalog need no ids; others need connection_id or create fields.
labelNocreate/configure: human name for the source, e.g. "Freshdesk".
queryNomode=catalog only: filter by name, category or description.
configNocreate with provider: catalog required_fields; stored encrypted.
toolkitNocomposio action modes: Composio app slug (e.g. "freshdesk").
providerNomode=create: NATIVE provider from catalog native_providers (with config).
pull_toolNocomposio_create: read-only daily action from composio_actions.
recipe_idNomode=create: catalog recipe id (curated mapping).
json_pathsNocreate/configure: dotted paths into the payload body.
rate_limitNocreate/configure: max requests/min accepted. Default 100.
sync_everyNoPULL sources only: cadence. Default daily.
trigger_slugNocomposio_create, INSTANT apps: trigger from composio_catalog.
connection_idNoConnection id (mode=list); required by configure/pause/resume/sync_now/delete.
pull_argumentsNocomposio_create with pull_tool: action arguments.
collection_pathNocomposio_create + pull_tool: dotted path to the record array.
source_categoryNomode=create with your own mapping: what the payload carries.
skip_attributionNocreate: anonymous public-forum sources have no attributable customer.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / recipe_id / description
      Previous value: -"mode=create: catalog recipe id — applies its curated mapping."New value: +"mode=create: catalog recipe id (curated mapping)."
  2. Changed9 schema fields changed
    • changedInput schema / properties / collection_path / description
      Previous value: -"composio_create with pull_tool: dotted path to the record array if not inferable."New value: +"composio_create + pull_tool: dotted path to the record array."
    • changedInput schema / properties / config / description
      Previous value: -"mode=create with provider: catalog required_fields. Stored encrypted, never readable again."New value: +"create with provider: catalog required_fields; stored encrypted."
    • changedInput schema / properties / connection_id / description
      Previous value: -"Connection id from mode=list; required for configure/pause/resume/sync_now/delete."New value: +"Connection id (mode=list); required by configure/pause/resume/sync_now/delete."
    • changedInput schema / properties / json_paths / description
      Previous value: -"create/configure: dotted paths into the POSTed payload's JSON body."New value: +"create/configure: dotted paths into the payload body."
    • changedInput schema / properties / provider / description
      Previous value: -"mode=create: NATIVE provider from catalog native_providers. Pair with config."New value: +"mode=create: NATIVE provider from catalog native_providers (with config)."
    • changedInput schema / properties / pull_tool / description
      Previous value: -"composio_create, DAILY apps: read-only action from composio_actions."New value: +"composio_create: read-only daily action from composio_actions."
    • changedInput schema / properties / rate_limit / description
      Previous value: -"create/configure: max requests per minute accepted. Default 100."New value: +"create/configure: max requests/min accepted. Default 100."
    • changedInput schema / properties / skip_attribution / description
      Previous value: -"mode=create: true for anonymous public-forum sources with no attributable customer."New value: +"create: anonymous public-forum sources have no attributable customer."
    • changedInput schema / properties / toolkit / description
      Previous value: -"composio_actions / composio_create: Composio app slug (e.g. \"freshdesk\", \"jira\")."New value: +"composio action modes: Composio app slug (e.g. \"freshdesk\")."
  3. Changed1 schema field changed
    • addedOutput schema / properties / result
      Added value: +{}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {},
      +  "type": "object"
      +}
  5. Changed2 schema fields changed
    • changedInput schema / properties / connection_id / description
      Previous value: -"Connection id from mode=list; required for configure/pause/resume/sync_now."New value: +"Connection id from mode=list; required for configure/pause/resume/sync_now/delete."
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "list",
      -  "catalog",
      -  "create",
      -  "configure",
      -  "pause",
      -  "resume",
      -  "sync_now",
      -  "composio_catalog",
      -  "composio_actions",
      -  "composio_create",
      -  "composio_authorize"
      -]New value: +[
      +  "list",
      +  "catalog",
      +  "create",
      +  "configure",
      +  "pause",
      +  "resume",
      +  "sync_now",
      +  "delete",
      +  "composio_catalog",
      +  "composio_actions",
      +  "composio_create",
      +  "composio_authorize"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / collection_path / description
      Previous value: -"composio_create with pull_tool: dotted path to the record array, when not inferable."New value: +"composio_create with pull_tool: dotted path to the record array if not inferable."
    • changedInput schema / properties / pull_arguments / description
      Previous value: -"composio_create with pull_tool: arguments the action needs."New value: +"composio_create with pull_tool: action arguments."
  7. Changed4 schema fields changed
    • changedInput schema / properties / json_paths / properties / deep_link_url / description
      Previous value: -"Path to a URL that opens the item in the origin tool."New value: +"Path to a URL opening the item in the origin tool."
    • changedInput schema / properties / json_paths / properties / occurred_at / description
      Previous value: -"Path to the timestamp; without it ingestion time is used."New value: +"Path to the timestamp; else ingestion time."
    • changedInput schema / properties / json_paths / properties / raw_text / description
      Previous value: -"REQUIRED: path to the customer's own words, e.g. \"ticket.description\" or \"text\"."New value: +"REQUIRED: path to the customer's own words, e.g. \"ticket.description\"."
    • changedInput schema / properties / source_category / description
      Previous value: -"mode=create with your own mapping: what kind of signal the payload carries."New value: +"mode=create with your own mapping: what the payload carries."
  8. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With annotations declaring readOnlyHint=false and destructiveHint=true, the description adds important behavior: delete is a soft-disconnect, create returns an endpoint, and the signing secret is shown only once and must be relayed immediately. It also clarifies that Atisbo reads from the connected system rather than writing into it. Some operational details about pause, resume, and sync_now remain unspecified.

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 short, front-loaded with the resource and mode list, and every sentence adds useful information. The catalog warning and secret-handling warning are both justified and tightly stated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an 18-parameter, multi-mode tool with an output schema, the description covers the high-level mode set, catalog exception, read-only source behavior, and secret handling. However, it leaves several operational details unexplained, including what pause/resume/sync_now do and how soft-disconnect affects existing data.

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 description coverage is 100%, so the input schema already documents most parameters in detail. The description adds a few semantic points, such as the one-time signing secret and soft-disconnect behavior, but it does not meaningfully enrich most individual parameter meanings beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource as "WHERE Atisbo gets its signals" and lists concrete modes (list, catalog, create, configure, pause, resume, sync_now, delete). It clearly identifies the tool's domain as intake source connection management, though it does not explicitly compare itself with the sibling tools.

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?

It gives one concrete usage rule: call catalog and read `fallback` before saying Atisbo cannot ingest something. It does not explain when to use this tool instead of siblings such as atisbo_capture or atisbo_lookup, so guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources