List integrations
magicbell_list_integrationsRead-only
List configured provider integrations (e.g. Sendgrid, APNs, FCM). Project API: GET /integrations.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
magicbell
by io.usefulapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true. Description adds endpoint and examples but no additional behavioral context beyond that.
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?
Single sentence, no wasted words. Efficiently conveys purpose and endpoint.
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?
Annotations cover read-only nature, description includes examples and endpoint. No output schema, but return values are implied. Adequate for a simple list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters, so schema coverage is 100%. Description doesn't add parameter info, but none is needed. Baseline 4 for zero params.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'List configured provider integrations' with examples, distinguishing it from sibling tools that list other entities.
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?
No explicit when-to-use or alternatives, but for a simple list tool with no parameters, usage is implied. Lacks exclusionary context.
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.
TDQS
A4/5.0
Disambiguation5/5
Each tool targets a distinct resource and action (create, get, list, update) with no overlap. Verbs and nouns are clearly separated.
Naming Consistency5/5
All tools follow a consistent 'magicbell_verb_noun' pattern, with verbs (create, get, list, update) and singular/plural usage appropriate to the operation.
Tool Count5/5
13 tools cover core user management, broadcast/event observability, and configuration listing without being excessive or sparse for a notification platform.
Completeness4/5
Covers user CRUD (missing delete), broadcast/event/get/list, and configuration listing. While some write operations are absent, the set supports essential admin and observability tasks.