Skip to main content
Glama

Atisbo

by io.github.brian8a1
OverviewDiscussionsAdmin

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 (push app, daily-pull app, raw webhook/email) — call catalog and read fallback before ever saying "Atisbo cannot ingest that". Atisbo only READS a connected system. create returns endpoint + signing secret shown ONCE — relay to the human immediately.

Input Schema

TableJSON 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.
configNomode=create with provider: catalog required_fields. Stored encrypted, never readable again.
toolkitNocomposio_actions / composio_create: Composio app slug (e.g. "freshdesk", "jira").
providerNomode=create: NATIVE provider from catalog native_providers. Pair with config.
pull_toolNocomposio_create, DAILY apps: read-only action from composio_actions.
recipe_idNomode=create: catalog recipe id — applies its curated mapping.
json_pathsNocreate/configure: dotted paths into the POSTed payload's JSON body.
rate_limitNocreate/configure: max requests per minute accepted. Default 100.
sync_everyNoPULL sources only: cadence. Default daily.
trigger_slugNocomposio_create, INSTANT apps: trigger from composio_catalog.
connection_idNoConnection id from mode=list; required for configure/pause/resume/sync_now/delete.
pull_argumentsNocomposio_create with pull_tool: action arguments.
collection_pathNocomposio_create with pull_tool: dotted path to the record array if not inferable.
source_categoryNomode=create with your own mapping: what the payload carries.
skip_attributionNomode=create: true for anonymous public-forum sources with no attributable customer.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / result
      Added value: +{}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {},
+  "type": "object"
+}
  3. 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"
+]
  4. 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."
  5. 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."
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful nuance beyond them: delete is a 'soft-disconnect', the create secret is shown ONCE and must be relayed, and the tool only READS the connected system. These are non-obvious behaviors an agent needs. It doesn't cover rate-limit or failure semantics, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The most important constraint (catalog is not the boundary) and the one-time-secret warning are front-loaded and emphatic. It is dense but each sentence carries operational weight; the all-caps emphasis is slightly noisy but not wasteful.

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

Completeness4/5

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

For an 18-parameter, multi-mode tool with an output schema and destructive annotations, the description covers the mode taxonomy and the key gotchas (fallback catalog, one-time secret, soft delete). Combined with the rich schema, an agent has enough to call it correctly, though mode-to-parameter mapping remains inferential.

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 schema already documents all 18 parameters including mode enums and per-mode requirements. The description adds the mode vocabulary and which modes need ids, but no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 tagline 'WHERE Atisbo gets its signals' plus the explicit mode list (list, catalog, create, configure, pause, resume, sync_now, delete) states a concrete resource and its operations, distinguishing it from siblings like atisbo_capture or atisbo_analyze. It is clear what the tool manages, though the opening metaphor is less literal than a plain verb+resource statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives actionable when-to-use guidance: call catalog and read `fallback` before declaring a source unsupported, and relay the one-time secret to the human immediately. It does not explicitly contrast against sibling tools (e.g., when to connect vs. capture), so it stops short of full routing guidance.

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

All Atisbo toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources